CircuitPython install issues

7alken

Hi, I tried to follow Getting Started with CircuitPython here:
https://developer.sony.com/develop/spresense/docs/circuitpython_set_up_en.html

but, first, "flash_writer.exe" to download from here is BAD 16-bit incompatible with Win10 64-bit -- well, I used one from spresense-sdk downloaded by msys2

then I tried to update bootloader using msys2 to lastest 2.3.0, but then realized you have recommended 2.0.2 - I tried both of them after few tweaks to windows commands for flashing, as they seem to be incorrect too (using latest flash_write.exe from SDK):
-- tried flashing from msys2 and also then found way how to specify cmdline in windows shell too as below:

bootloader:
flash_writer.exe -s -c COM14 -b 115200 -d -n -s ./AESM.espk ./dnnrt-mp.espk ./gnssfw.espk ./loader.espk ./sysutil.spk

then flashing circuitpython:
flash_writer.exe -s -c COM14 -b 115200 -d -n adafruit-circuitpython-spresense-en_US-7.0.0.spk

(lots of ACK/NAK issues during uploading firmware also)

BUT finally ... as I have main board inserted in extension board, it seems that on mainboard micro-usb, there is no "CIRCUITPY" available after flash ... "some" TRIES to be available on the extension board mass-storage micro-usb though .. (yet without serial console) AND this "CIRCUITPY" is totally unstable and failing after first show, absolutely unusable ... I know, that this may be CP firmware fault, ya, but can somebody with appropriate power to try to notify adafruit about the issue also from here??

Thanks,
Petr

KamilTomaszewski

Hi @7alken

The flash_writer.exe from Spresense SDK is the same as the one that is posted here: https://developer.sony.com/develop/spresense/docs/circuitpython_set_up_en.html. This is the link to the Spresense SDK github.

The USB classes on Spresense CircuitPython are available on micro USB on the extension board, not on the main board. The main board USB is only used for flashing.

I created a PR that should fix the issue you are writing about: https://github.com/adafruit/circuitpython/pull/5635

Does your problem only occur when you use the time.time() function?

Best Regards,
Kamil Tomaszewski