K10 + MicroPython
AntonioBenci 2025-05-10 08:59:59 896 Views5 Replies I have a very annoying and persistent issue with the K10 module running MicroPython (unihikerK10mpy_20241122_V0.5.bin).
On the initial connection and the first time loading load of a file script, using either Mind+ or Thonny, the “boot.py” python script will run and operate as expected.
Thereafter, any attempt to halt “boot.py” script from running and attempting to edit and reload, is not possible. The module is frozen and all comms are blocked.
The only way to recover is to reload the MicroPython firmware.
Any suggestions would be appreciated.
This is a known bug in the current MicroPython and will be fixed in the next MicroPython update.
The next version of MicroPython will be available soon.
Yeez_B The examples on the Wiki are not mentioned to be placed in boot.py. Conceptually, the examples should be used in the main.py file. In MicroPython, the boot.py file is executed once on boot-up, before any other scripts like main.py. It is used primarily for system configuration, especially related to hardware setup, network configuration, and initialization that must happen before the main application logic runs.
I tested (not the examples directly) and had no issues yet (with code execution). I only don't like that currently REPL does not work, as expected.
Yes, you can use other Firmware (downloaded from MicroPython) and few issues like RAW REPL via standard tools which are already know by DFRobot get solved. Yes, you can also create (build) own Firmware and also there few issues get solved. Yes, you can flash CircuitPython instead MicroPython and few issues are solved. The problem with such solutions is that required modules, which you normally import (unihiker_k10) will not be available and you will have to write everything by your self! That makes the usage for many inexperienced users much harder, goes on coasts of performance (except you build firmware with C/C++ and/or *.mpy). I think currently there would be better options! First option: we all report issues and wait that these are fixed soon in newer versions. Second option: DFRobot will share the code repository and all of us could support. Third option: (near by 2nd) we get read access to repository and could select which modules we like to have in our own firmware.
Lupin Hi Lupin.
A correction at my end, I meant “code.py” not "boot.py". That was my mistake.
When I run the examples, and I have used “hello_unihiker” to test, the REPL will randomly lock-up.
I'll wait for the updated Micropython firmware.
In the meantime, I've had some good success in using Circuitpython for testing. The only limitation being the graphics.
Cheers.
Could you post the code of your boot.py?
Lupin The code that I was trying to run is the code example given at
https://www.unihiker.com/wiki/K10/Examples/examples_mpy/
No changes to the code, copied to boot.py as is. Once the code is run, the REPL will cease to work, no response.
The only way to obtain a response is to reinstall the MicroPython BIN file;
unihikerK10mpy_20241122_V0.5.bin
from;
https://drive.google.com/file/d/1gKTtFghDu0V-vSi19ahH7bor5WSaBbDE/view?usp=drive_link
In the interim, and to test the hardware, I have loaded a generic version of MicroPython;
https://micropython.org/resources/firmware/ESP32_GENERIC_S3-SPIRAM_OCT-20250415-v1.25.0.bin
Which works without fault. even though it does not have the specific bindings and libraries that the Unihiker version has, I can run almost all generic MicroPython code, excepting the code required for the ILI9341 LCD.
I hope this helps.
Regards, Antonio Benci
