New device: Cat-M1 and NB-IoT upgrade

[mfalkvidd]

Hi.

I've unpacked my first Pycom devices (a GPy and a FiPy, focusing on the GPy for now). I want to use the GPy with Hologram.

https://forum.pycom.io/topic/2902/cellular-radio-firmware-release-sqn3330-for-both-cat-m1-and-nb-iot says

Cellular radio firmware release (SQN3330) for both Cat-M1 and NB-IoT"

But https://docs.pycom.io/chapter/tutorials/lte/firmware.html says

If your module is running the factory LTE chip firmware, you MUST first perform an update to the latest CAT-M1 firmware before trying to upgrade to the NB-IoT firmware"

Do I need to upgrade the CAT-M1 firmware before performing the instructions in https://forum.pycom.io/topic/2902/cellular-radio-firmware-release-sqn3330-for-both-cat-m1-and-nb-iot ?
If so, can I follow the same instructions, but use the FIPY_GPY_CATM1_36417.dup file instead of FIPY_GPY_NB1_35351.dup? Or does the CAT-M1 firmware require a different upgrade method?

I'm asking since upgrading the modem firmware seems to be delicate and doing the wrong thing could make it very hard to recover my GPy.

[dan]

Hi @agotsis, Please check this post for more info about this issue. Hope this helps!

[agotsis]

@xykon Are there any updates for resolving the firmware upgrade error?

[agotsis]

This post is deleted!

[Xykon]

@agotsis Unfortunately it looks like you ran into one of two issues I identified with Sequans which cause the LTE modem to become unresponsive.

We are still waiting for Sequans to produce a permanent solution that will allow us to fix both issues permanently to make sure the modem is always recoverable.

I am working on making documentation available that will allow accessing the modem console logs through one of the test points on the bottom of the module. This will help us identify the exact issue (or issues) causing this.

I will post more as soon as possible.

[agotsis]

@xykon I actually added the resume=True to address the "AT+SMSWBOOT=3,0 Failed!" error as mentioned in another post... If I leave resume out of the game I am stuck in that point.
I am now trying to repeat the procedure using an SD card.

UPDATE: And this is the error I get when using the SD card:

Entering recovery mode
AT+SMSWBOOT=3,0 response b''
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "sqnsupgrade.py", line 130, in run
OSError: AT+SMSWBOOT=3,0 failed!

Thanks!

[Xykon]

@agotsis The resume=True option will only work if the modem is already in upgrade mode.

What do you get when you power-cycle the module and run the upgrade without the resume option?

[agotsis]

@xykon I just tried to install the latest NB-IoT firmware to my FiPy connected to a PyTrack board. Prior to this I have successfully installed FiPy-1.18.0.r1.tar.gz. Unfortunately I am stuck in the following point:

>>> sqnsupgrade.run('/home/gotsis/FIPY_GPY_NB1_37781.dup', 921600, port='/dev/ttyACM0',resume=True)
<<< Welcome to the SQN3330 firmware updater >>>
Starting STP (DO NOT DISCONNECT POWER!!!)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/gotsis/git/pycom-libraries/lib/sqnsupgrade/sqnsupgrade.py", line 144, in run
    raise OSError("Invalid answer '%s' from the device" % response)
OSError: Invalid answer 'b''' from the device

As seen from the code I am running this through the serial port, not an SD.
Any ideas, suggestions?

Many thanks!

[Xykon]

@le_wildfox A new NB-IOT firmware 37781 is now available. I have also updated the upgrade scripts so please make sure you fetch the latest version.

[le_wildfox]

@xykon Thanks for your response. As I'm currently working on prototype which should work with Huawei powered NB-IoT network, really hope to hear from you soon if the tests have been completed and the new firmware has been made available.
Last time I tried on their test lab, all I got was something like:

+CEREG : 2,4

Cheers!

[Xykon]

@le_wildfox We have a new firmware that I'm testing right now. We also received a new bootrom that will allow recovery if the flashing fails. I'm testing all this now and will provide more details as soon as possible.

At the moment I would suggest to refrain from trying to use the new NB-IoT firmware until the update is available. I'm trying as hard as I can to make this available but at the same time I don't want to risk more people loosing access to their devices.

[le_wildfox]

@xykon Hello again, have you got any news about the failed upgrade using new firmware below?
Big thanks!

[le_wildfox]

@xykon oh, okay. However I have this issue when upgrading:

https://forum.pycom.io/topic/3460/new-cat-m1-nb-iot-firmware-10-july-2018-upgrade-failure:

Any way to resolve it?
Thanks!

[Xykon]

@le_wildfox I was told by the LTE team that the upgrade order doesn't actually matter. I'm planning to do a few more tests today before updating the instructions.

[le_wildfox]

@xykon Thanks!
I'm currently trying to upgrade with the new firmware.

So the upgrade sequence should be:
step 1. upgrade to new CAT-M 36417.dup
step 2. upgrade to new NB1 37365.dup

Is that correct?

[Xykon]

@le_wildfox It is now available for download: sequans.html or directly FIPY_GPY_NB1-37365.dup

[le_wildfox]

@xykon

Is there any update on support for nb-iot with huawei equipments?
Any timeline maybe?

Thanks!

[Xykon]

@mfalkvidd I just checked with the LTE team... it turns out this requirement can be ignored. I will update the instructions shortly.