New firmware release v1.17.0.b1 (Completely new LTE class)

[robert-hh]

@daniel @Xykon @seb Thanks for the Linux software updater. I ignored that since a while, and I am still not using it for software updates, but it has a lot of other management options, which are very useful.

[losi]

@seb Your link points to release v1.12.0.b0, which is why i asked.

[rskoniec]

@losi said in New firmware release v1.17.0.b1 (Completely new LTE class):

@seb Your link points to release v1.12.0.b0, which is why i asked.

Let's clear something:
v1.12.0.b0 is the newest version of the Updater Tool.
v1.17.0.b1 is the newest version of the Firmware.

So @seb gave you right answer.

[Neuromystix]

@jcaron with my tests that's the behavior.

• With ADR enabled, it start with DR0 and change when LS send LinkADRReq.
• With ADR disabled, Lopy started with DR defined in setsockopt. In this case LorawanServer don't send LinkADRReq command, when we try to manually adjust DR. Since ADR bit is disabled, i suppose that LS don't even try to send the command.

[Colateral]

@colateral Backtrace output:

Decoding 8 results
0x400dbec8: system_get_rtc_time at /Users/danicampora/Code/Espressif/IDF/esp-idf-20180112/components/newlib/./time.c line 261
0x4009a73c: memcpy at /home/jeroen/esp8266/esp32/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/machine/xtensa/../../../../.././newlib/libc/machine/xtensa/memcpy.S line 168
0x4009a76a: memcpy at /home/jeroen/esp8266/esp32/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/machine/xtensa/../../../../.././newlib/libc/machine/xtensa/memcpy.S line 201
0x400dbec8: system_get_rtc_time at /Users/danicampora/Code/Espressif/IDF/esp-idf-20180112/components/newlib/./time.c line 261
0x40084c65: SX1272OnDioIrq at D:\Colateral\Programming\pycom\pycom-micropython-sigfox\esp32/../drivers/sx127x/sx1272/sx1272.c line 1039
0x40083f0b: machpin_intr_process at D:\Colateral\Programming\pycom\pycom-micropython-sigfox\esp32/mods/machpin.c line 187
0x40083585: _xt_lowint1 at /Users/danicampora/Code/Espressif/IDF/esp-idf-20180112/components/freertos/./xtensa_vectors.S line 1105

[losi]

@rskoniec Okay, so I can use the v1.12.0.b0 updater tool, which I have installed. I also see the selection for uploading alternate firmware.

Now where is the v1.17.0.b1 image hiding? I don't see any link on this post containing this image.

[robert-hh]

@losi I think it's selected automagically. But besides that, all files are here: https://github.com/pycom/pycom-micropython-sigfox/releases/tag/v1.17.0.b1
You will need one of the xxx.tar.gz files.

[losi]

@robert-hh Thank you! That is exactly what I was looking for.

[IOAg]

@daniel no mention of fipy LTE issue with Telstra in Australia. Any chance release includes a fix?

[nathanh]

@ioag said in New firmware release v1.17.0.b1 (Completely new LTE class):

@daniel no mention of fipy LTE issue with Telstra in Australia. Any chance release includes a fix?

So I still cannot connect to Telstra. However, it is nice to have AT command access which has given some more control and feedback.

From my testing I will setup the APN with the following prior to trying to attach.

AT+CGDCONT=1,"IP","telstra.m2m"

If I then try and check the status with AT+CEREG? I get the result +CEREG:2,0 as you would expect.

When I then try to attach I get the following:

lte.attach()
lte.send_at_cmd('AT+CEREG?')
\r\n+CEREG:2,4\r\n\r\nOK\r\n

So the result of 2,4 is an unknown response (and according to doco, one possible reason can be no coverage). However, according to Telstra's coverage map I am under full coverage. I can confirm on my phone I do get Telstra 4G but whether on not the phone is using band 28 like the device should be, I am unable to determine.

Anyway, still disappointing that a product being sold here and was meant to be certified according to Pycom's website last year (https://pycom.io/state-lte-m/) is still not working. Especially since everything else Pycom has been awesome to work with. At this stage I might start looking at going back to working with the ESP32 direct with a Telit modem.

[incognico]

@seb said in New firmware release v1.17.0.b1 (Completely new LTE class):

@losi
The links at the top of this page should always point to the latest version:
https://docs.pycom.io/chapter/gettingstarted/installation/firmwaretool.html

What links at the top of this page? Maybe I need some more coffee this morning but I couldn't see a link to this new tool "at the top of this page". A search of the page source doesn't find a link to firmwaretool.html until your post. Even if it is there and I'm being foolish, perhaps a more obvious link to the tool when announcing it would be helpful...?

[livius]

@daniel
Is there some progress about point 3 from this post? :)
https://forum.pycom.io/post/15420

Encryption: Complete flash encryption will be supported with an AES-256 key stored in the fuse bits of the ESP32. Reading this key from outside of the ESP32 is not possible. In addition, we will add secure boot which writes protect the bootloader area. Both measures will make the firmware flashed to our modules fully secure. Expect this update before end Feb.

[danielm]

@Xykon
I sent a mail to support@pycom.io as you suggested in this post:
https://forum.pycom.io/topic/2734/new-firmware-release-v1-17-0-b1-completely-new-lte-class/8

[nathanh]

@IOAg @danielm just an update I got my FiPy working on Telstra with your latest firmware. Details posted here: https://forum.pycom.io/topic/2769/telstra-lte-cat-m-working-on-fipy-just

[bali]

@daniel

Just updated Gpy to new firmware but as soon as i call the LTE class it crashes. Any idea why?

import os
os.uname()
(sysname='GPy', nodename='GPy', release='1.17.0.b1', version='v1.8.6-849-d0dc708 on 2018-02-27', machine='GPy with ESP32')
from network import LTE
lte=LTE()
/Users/danicampora/Code/Espressif/IDF/esp-idf-20180112/components/freertos/./queue.c:718 (xQueueGenericSend)- assert failed!
abort() was called at PC 0x40089fb8 on core 1

[livius]

@daniel
Is there possibility to store variables in rtc memory from python code?
This memory survive deep sleep.
This is already avaiable by RTC_DATA_ATTR to declare variable stored in RTC memory.

[daniel]

@livius yes, this is part of the roadmap. Expect it in a few weeks.

[Colateral]

@liviue I can not find this RTC_DATA_ATTR in documentation. Can you post an example?

[livius]

@colateral said in New firmware release v1.17.0.b1 (Completely new LTE class):

RTC_DATA_ATTR

only from source code and custom firmware
not available in python
you can find details here:
https://github.com/pycom/pycom-esp-idf/blob/master/components/esp32/include/esp_attr.h

[Colateral]

@livius ahhh.. thanks :)