@jmarcelino said in CPU Frequency: I changed it, but got the same results. Mike

@robert-hh I see that in current 1.7.2 it is fixed - all calculations are cast to uint64 and also constants are with ull suffix https://github.com/pycom/pycom-micropython-sigfox/commit/3284efccc8e4488a56c4cc93a494a58d6b348908

@robert-hh said in Update LoPy firmware using Pysense as expansion board: So better never supply the board by the 3.3V Pin. That's an output, not an input. Use the Vin Pin for supply. @daniel: Please remove note, that the device can be supplied through the 3.3V pin. Even if that may work under certain conditions, the risk is too high that devices will be broken. I see that we disscuss this 6 months ago ;-) https://forum.pycom.io/topic/316/wipy-pin-3v3-not-work But conclusion was different. Now when we have schematic i do not see there any diode or something like LTC4357 And schematic(and description) for LM3281 does not bring light if there is some protection - especially that there is comparator output

@patrick The stable release 1.18.0 uses Micropython 1.8.6, the developement release 1.19.2 is based on Micropython 1.9.4

I managed to find a USB-to-serial adapter and tried some things with that. My Windows machine won't recognize it, and on my mac I can't figure out what tty port it's on. I did however dig out a Raspberry Pi where it seem to work. Unfortunately it didn't help, because the linux-version of the pycom updater just keeps saying "Something failed trying to connect to the device." and then gives no further info. I also tried modifying the baud rate in the updater.py script as some thread suggested, but no luck.

For the moment , my code is working with ESP-IDF on an ESP32 board , but i need LoRa support . Will try to add the LoRa stack working for the SX1272. By the way , is there a way to know the ESP framework version used by the LoPy ? in Python , got no detection from some of my BT beacons ( same problem using 3 LoPy board) , but it's more like its an ESP IDF problem- link May be it would be solved in futur firmware ?

@Arkaik In the list of commits, you have to go back to an entry with the title "Bump to version 1.4.0.b1". There you find the fingerprint. It's not a long way. In you first port you mentioned 1.4.0b1. But now you mention 1.0.4b1. About esp-idf. Do use the version indicated by the pycom web site.Try to checkout the most recent version before the date of the wipy firmwar you are using. That might get a little bit of a trial & error game.

@markj use ubinascii.hexlify(string) to covert it to hex-ASCII.

Thanks for the details on boot mode @jmarcelino, PyCom could put a bit more detail in the docs regarding this - the pin out diagram suggests it should work regardless and that it is working now, not a to be added feature. Regarding the firmware update issue I have resolved it :-) Turns out I was needing a pull-up resistor on the Reset pin - my guess is that noise from the serial pins was enough to cause a reset during the update or maybe I was just lucky the the time I added the resistor. I was also able to recover my second board with the resistor in place adding weight to the pull-up being required theory. Thanks for everyone's help. Cheers Dave

@Immondizia The current repo is pycom-micropython-sigfox for all 3 boards

os.uname()

@mrainone @daniel Behavior confirmed. I added a few print statements between the lines to see where it fails. Sometimes it passed through the script, sometimes it just stalled, sometimes I get an guru mediation error. In case of failure, it happened at the statement: sd = SD() Pasting the scripts into REPL always works. The core dump starts with (calling for saint Daniel): /Users/danicampora/Code/Pycom/esp-idf-2017-03-12/components/freertos/./queue.c:1444 (xQueueGenericReceive)- assert failed! abort() was called at PC 0x40085501 Guru Meditation Error: Core 0 panic'ed (abort) Backtrace: 0x40008155:0x3ffc5670 0x40007d16:0x3ffc5690 0x40125065:0x3ffc56d0 0x4019e230:0x3ffc5700 0x401977b4:0x3ffc5720 0x40197ba6:0x3ffc5770 0x400e0ee0:0x3ffc57a0 0x400df756:0x3ffc57f0 0x400f2b8e:0x3ffc5830 0x400eace0:0x3ffc5850 0x400f62e8:0x3ffc5870 0x400ee697:0x3ffc5910 0x400eace0:0x3ffc5990 0x400eb776:0x3ffc59b0 0x400f3d46:0x3ffc5a40 0x400f40b5:0x3ffc5a70 0x400eb602:0x3ffc5b50 0x400f65d4:0x3ffc5b90 0x400ee697:0x3ffc5c30 0x400eace0:0x3ffc5cb0 0x400ead09:0x3ffc5cd0 0x400d8c38:0x3ffc5cf0 0x400d8eb3:0x3ffc5d80 0x400d7f76:0x3ffc5dc0 ================= CORE DUMP START ================= YCgAAAwAAABsAQAA 6D38P7BV/D9QX/w/ wFT8P/Be/D8ubAAA7Dr8P+w6/D/oPfw/5Dr8PxQAAAAMf/s/DH/7P+g9/D8AAAAA BQAAAFQ//D9NaWNyb1B5AAAAAAAAAAAAAAAAAFBf/D8AAAAAIQAGAAUAAAABAAAA AAAAAMhm/D8AAAAAAAAAAAAAAAC4MPs/IDH7P4gx+z8AAAAAAAAAAAEAAAAAAAAA iKNCPwAAAABIHQBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAA== KYEIgFWBAEA2BwYAFn0AgHBW/D97AAAAewAAABAAAAD/////AAAAAOv///9UOfw/ AQAAACQAAAAkAAAACAAAAP////8AAAAA/////wUAAAABAAAAAAAAAODCAED2wgBA AAAAAAgAAAD/////aBAIQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

@robert-hh Thanks for that specific detail. It is especially interesting to have a mode for both. I was not aware of that to be possible. Currently I got my LoPy connected (to my other wlan). It was a failure to get an IP address in the first wlan. I may have some issues with that wlan. Now I have setup a dns name in my lan and can reach the gateway by it's name. The next step is to get it registering with TTN :-)

@robert-hh Thank you. I will work on that advice.

I have noticed since the previous firmware that ftp and telnet performance has dipped for the lopy. It is very slow especially while using the telnet REPL prompt. UART REPL prompt shows no issues at all though. Does anyone face a similar issue?

@Butch See this link about downgrade: https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users V1.6.8b2 links are canonically derived according to the list: https://software.pycom.io/downloads/LoPy_868-1.6.8.b2.tar.gz or https://software.pycom.io/downloads/LoPy_915-1.6.8.b2.tar.gz or https://software.pycom.io/downloads/WiPy-1.6.8.b1.tar.gz