@robert-hh said in Security - IP Protection: @catalin Don't forget to lock the JTAG interface (if possible). There is a fuse to disable JTAG (JTAG_DISABLE). Furthermore, unless you build a firmware with DEBUG enabled, the JTAG IO pins are re-initialised as inputs with pull-down enabled during micropython startup.

I've queried our firmware team about this and the response was: The IDF had a bug there at the beginning, so we disabled it He is welcome to enable it and submit a pull request

@xykon I just tried it and it seems to work. Thank you very much! Are the settings in examples/wifi/scan/sdkconfig in the Pycom IDF repository exactly what you are building with or do you use a modified version? Is it documented anywhere which version of the IDF was used in a particular version of MicroPython? I assume at lot of the settings in sdkconfig (for example partition table) don't really matter, because they only change the (in this case unused) bootloader and app that are also built with make all. Is this correct? I think a hint in the readme.md of the Pycom IDF would be helpful.

@mrainone said in function removed from LIS2HH12.py library module: can you recommend a low cost magnetometer to connect to the lopy I use simple GY-271 (HMC5883L) It working fine for me and is cheap

@misterlisty Youj can dowload images, like https://software.pycom.io/downloads/WiPy-1.15.0.b1.tar.gz or https://software.pycom.io/downloads/LoPy-1.16.0.b1.tar.gz This archives contain a file called appimg.bin, which you have to use for OTA. The files system is kept during OTA, including boot.py and main.py

Hi @matt_the_w The OEM modules should be programmed over the main serial port. I don't know of any other reliable way (WiFi OTA could be an alternative but I don't recommend it for factory programming)

awesome, thanks for the clear answer.

@dhruv I have changed your device from 868MHz to 915MHz. Please re-run the firmware update tool to flash the new region.

@robert-hh I was thinking about that however I am not aware of a straightforward way how individual parameters could be updated by the application. The script would be frozen anyway. I was also thinking to move all parameters to NVS however the config also contains few strings which are not directly supported by the NVS right now. I think that the best solution will be to put default parameter values into Python script which will be frozen during build process. After boot it will be tested if NVS contains "init" flag and if not an initialization method will be called. Within this method individual parameters will be loaded from Python script to a dictionary which will then be dumped into json file stored in the internal file system. This will happen only during first boot after last firmware flashing.

@binux @jmarcelino thanks for the clarification

@livius Ok, thanks, appreciate the reply.

@charly86 For OTA you just need appimg.bin, if the other two files are already loaded. The esptool.py command line for that would look like: esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x10000 appimg.bin

@jmarcelino With pycom.wifi_on_boot(False), I started using rshell, which I truly enjoy. It allows me to keep on writing code with vim (instead of atom) whilst rendering the upload and running of scripts really easy. The rshell command line tool definitely also merits mentioning in the documentation.

There's no urgency on my part, I just thought that the community here would want to know whether or not a fix could be expected soon and I noticed that nobody had yet asked the question.

Hello, fileno method added here: https://forum.pycom.io/topic/1951/new-firmware-release-version-v1-9-2-b1 Cheers, Daniel

@bmarkus The deepsleep shield is a PIC10, the Pysense/track use a PIC16 (for the USB stack I'd imagine)