MicroPython Forum (Archive)

So if it is set up as pyb.Pin.board.USB_ID, then the USB code totally ignores that pin, and currently goes into Device mode? That would be excellent. I will test later today.

PA10 is the ID pin for the USB port on the PyBoard. It is grounded when the appropriate connector is inserted, indicating the port is to be set up as a OTG Host. It would be nice to have a way (in Pins?) to have MicroPython ignore it, and go into Device mode. I have not seen anything on the forum wh...

One more caution- it appears the ADCAll method sets All possible pins to analog inputs. If you just want to get the counts from vref, it is on channel 17. Although the Micropython documentation says the argument for the ADC() method must be a pin, it apparently accepts a channel: >>> >>> a = pyb.ADC...

It just dawned on me- Vbat must be the backup battery voltage, on Pin 1... On another Pyboard with no battery I get: Micro Python v1.4.2-48-g6f218d7 on 2015-04-30; PYBv1.0 with STM32F405RG Type "help()" for more information. >>> >>> import pyb >>> a = pyb.ADCAll(12) >>> a.read_core_vbat() 0.4190476 ...

On the other hand.... With a measured supply of 3.368V, my device is reporting a vbat of 3.085V, which is an error of 8.4%... I guess so long as it is stable, this can be calibrated out, but that seems a long way off.

I reworked the above data to get an Est. of the supply, and allowed Vr to be a parameter. I then played with Vr to minimize the rms error. This is what I got with Vr=1.204V, which seemed to be about the best for this data set. Vr= 1.204 Cts Vsup Est. error (%) e^2 1972 2.501 2.500 -0.03 0.00 1920 2....

That did the trick- all working fine now. Thanks to all who helped!

That did it! Got a 10K and 470 ohm (closest I could get at Radio Shack), and put them in. Voila! All looks the same as the Pyboard. Thanks for the help with what were just failures to follow the Pyboard closely enough, and RTFM. Perhaps others who are laying out with this chip can avoid the wasted t...

I downloaded the latest DFU program from ST (3.04). It fixes the bug in 3.03 which caused the program to bomb when verifying. The "Verify" now passes successfully, so I know the code is in there! But still no COM or memory.

I may have spoken too soon! Everything loads okay, but I do not see a virtual COM port, or the USB drive that I would expect, when I let BOOT0 go low and do a reset. The DFU device in Device Manager goes away. Oscillator is running great at 8MHz all the time. I have done up Upgrade from the DFU Demo...