With the columns: in the .py file, scan_pin_file has some offsets as arguments. I guess it'd be nice if it worked them out from the CSV headings really...
Glad it's actually working though - if the serial is working at 9600 baud it means all the clock divisors are right too.
It's quite likely it's to do with 'USB disconnect' - there's usually a resistor that connects one of the USB data lines to 3.3v (which signals that there's a USB device on the line). The F4 appears to have that built-in, so there might be some problem activating it.
The good news is once that is fixed, the F429 discovery will probably spring into life too!
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Thanks!
With the columns: in the
.py
file,scan_pin_file
has some offsets as arguments. I guess it'd be nice if it worked them out from the CSV headings really...Glad it's actually working though - if the serial is working at 9600 baud it means all the clock divisors are right too.
So I'd take a look at https://github.com/espruino/Espruino/tree/master/targetlibs/stm32f4/usb and https://github.com/espruino/Espruino/tree/master/targetlibs/stm32f4/usblib and try and compare them with ST's examples for the F401. My guess is there's something a bit different in the USB initialisation.
It's quite likely it's to do with 'USB disconnect' - there's usually a resistor that connects one of the USB data lines to 3.3v (which signals that there's a USB device on the line). The F4 appears to have that built-in, so there might be some problem activating it.
The good news is once that is fixed, the F429 discovery will probably spring into life too!