MicroPython Forum (Archive)

Time to finish off this thread with what I found. The machine implementation of I2C definitely fixed the I2C issue. I'm not sure I mentioned exactly what that was. At startup it initally could do a scan() and get all the devices but later on during startup, w/o doing anything with I2C, it "lost" tha...

Thanks for your continuing suggestions. I'm working on them. An initial test seems to indicate that the machine implementation of I2C may help. Standby, I'll update when I have something more definitive to say.

OK, I'm getting the issue narrowed down. I did the bulk erase, as well as in the process upgraded the firmware to v1.12 from v1.11. Same issue, so that didn't solve it. On a hunch based on some other weird things that had been going on at startup for a few months (which I had a workaround kludge fix...

Thanks. It's good to know what it means. I'll work on those tests and post in a day or two.

Leds: red on, green on, yellow on, blue on (all 4 are then on), red off, green off, yellow off, blue off (all 4 are then off) ... then starts all over. Each on or off period is about a second. I've never written code that does that so I know it's not mine (smile). Windows 10 OS. I use a batch file t...

I can't find in the documentation what all 4 leds successively cycling on/off means.

I am having this issue at random with trying to establish a connection (with rshell) to a pyboard v1.1 (v1.12 software). Resetting the board to factory defaults does not fix it.

Thanks

Well, I wrote another test program, one that does not repeatedly cycle a led on/off but only toggles it if the USR switch is pressed. That way when not pressed it is only waiting for an interrupt. I measure a steady 33 mA. If I subract out 3 motherboard leds, 13 mA total, I'm left with 20 mA, which ...

The specs for the v1.1 board list 56 mA as the current consumption at 168 MHz as 56 mA running and 16 mA "idling". I have a simple test program that uses a timer interrupt every 250 ms to toggle one of the boards leds and waits for a pin to go low. My code is simply: set up timer interrupt to flash ...

Well, it was a battle, but I got it to upgrade. The link to the instructions on github were a big help. I had to do the whole zadig bit to get the WinUSB driver installed, and then use the dfu-util to do the upgrade. All went pretty much, but not completely, as described in that link. After I got df...

Both the red and the blue leds come on. Not terribly bright, but definitely on. I tried entering the bootloader with the REPL the way you suggest and the leds came on the same, and I could no longer issue a Ctrl-C with the REPL so I assume it was in DFU mode. Is there a way to upgrade with the REPL ...