Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    [Solved]Firmware upgrade tool for the Sequans Monarch SQN3330

    Scheduled Pinned Locked Moved FiPy
    fipy firmwarefipy
    17 Posts 2 Posters 3.7k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      DDA @jmarcelino
      last edited by

      @jmarcelino
      That was really a critical error on my part, I apologize . I have downloaded all the files again looks the same as on Git.
      I have the two *.dup files under /sd directory in my microSD card.

      >>>import sqnsupgrade
>>>
sqnsupgrade.run('/sd/FIPY_GPY_CATM1_33988.dup', 921600)

<<< Welcome to the SQN3330 firmware updater >>>
♦Traceback (most recent call last):
  File "<stdin>", line 3, in <module>
  File "/flash/lib/sqnsupgrade.py", line 72, in run
OSError: [Errno 2] ENOENT
♦>
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32
Type "help()" for more information.
      J 1 Reply Last reply Reply Quote 0
      • J Offline
        jmarcelino @DDA
        last edited by

        @dda
        Glad you got it going so far.

        Are you saying you placed the files into a folder called sd on the SD card? That's actually not necessary, the files should be directly on the root folder.

        The /sd is just a mount point for MicroPython

        D 1 Reply Last reply Reply Quote 0
        • D Offline
          DDA @jmarcelino
          last edited by DDA

          @jmarcelino
          Now I get AT+SMSWBOOT=3,0 failed.
          I removed the sd folder from the SD card, formatted it again to FAT32 and SD card now contains just the two *.dup files for CAT-M and NBIoT only on the root.

          On executing the following from main.py or from REPL I get the error:

          Connecting on COM25...

>>>
Uploading project (main folder)...

Reading file status
Failed to read project status, uploading all files
Creating dir lib
Creating dir workspaceStorage
Creating dir workspaceStorage/bc895fb1973b5d5624b4a2ed2625b38c
[1/8] Writing file lib/codec.py
[2/8] Writing file lib/crc.py
[3/8] Writing file lib/sqnsupgrade.py
[4/8] Writing file lib/stp.py
[5/8] Writing file main.py
[6/8] Writing file pymakr.json
[7/8] Writing file settings.json
[8/8] Writing file workspaceStorage/bc895fb1973b5d5624b4a2ed2625b38c/meta.json
Upload done, resetting board...
ets Jun  8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff8028,len:8
load:0x3fff8030,len:1728
load:0x4009fa00,len:0
load:0x4009fa00,len:14584
entry 0x400a059c
<<< Welcome to the SQN3330 firmware updater >>>
Entering recovery mode
Traceback (most recent call last):
  File "main.py", line 2, in <module>
  File "/flash/lib/sqnsupgrade.py", line 98, in run
OSError: AT+SMSWBOOT=3,0 failed!
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32
Type "help()" for more information.
>>>

          >>> import sqnsupgrade
>>> sqnsupgrade.run('/FIPY_GPY_CATM1_33988.dup', 921600)
<<< Welcome to the SQN3330 firmware updater >>>
Entering recovery mode
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/flash/lib/sqnsupgrade.py", line 98, in run
OSError: AT+SMSWBOOT=3,0 failed!
>>>
          J 1 Reply Last reply Reply Quote 0
          • J Offline
            jmarcelino @DDA
            last edited by

            @dda
            OK it's reading the files correctly. Can you try a couple more times? Make sure it's from a clean, freshly power up, start.

            D 1 Reply Last reply Reply Quote 0
            • D Offline
              DDA @jmarcelino
              last edited by

              @jmarcelino
              Ok repeated the following steps in order:

              1. Ran os.mkfs('/flash')
              2. Powered off Fipy/Expansion board 2.0
              3. Took out SD card, formatted the SD card and reloaded the CATM 's dup file into it.
              4. Powered Fipy on Expansion 3.0
                5 Started VSC software & Uploaded files
              Creating dir lib
Creating dir workspaceStorage
Creating dir workspaceStorage/bc895fb1973b5d5624b4a2ed2625b38c
[1/8] Writing file lib/codec.py
[2/8] Writing file lib/crc.py
[3/8] Writing file lib/sqnsupgrade.py
[4/8] Writing file lib/stp.py
[5/8] Writing file main.py
[6/8] Writing file pymakr.json
[7/8] Writing file settings.json
[8/8] Writing file workspaceStorage/bc895fb1973b5d5624b4a2ed2625b38c/meta.json
Upload done, resetting board...
ets Jun  8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff8028,len:8
load:0x3fff8030,len:1728
load:0x4009fa00,len:0
load:0x4009fa00,len:14584
entry 0x400a059c
<<< Welcome to the SQN3330 firmware updater >>>
Entering recovery mode
Traceback (most recent call last):
  File "main.py", line 2, in <module>
  File "/flash/lib/sqnsupgrade.py", line 98, in run
OSError: AT+SMSWBOOT=3,0 failed!
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32
Type "help()" for more information.
>>>

              Tried about 4-5 times now and about 3-4 times earlier to you reply.

              The FiPy is on a Expansion board 2.0 and powered via the USB connection to the PC.

              J 2 Replies Last reply Reply Quote 0
              • J Offline
                jmarcelino @DDA
                last edited by

                @dda
                Ok thanks, can you let me know the output of

                from network import LTE
lte = LTE()
lte.send_at_cmd('ATI')

                Thanks

                1 Reply Last reply Reply Quote 0
                • J Offline
                  jmarcelino @DDA
                  last edited by jmarcelino

                  @dda
                  Sorry just saw you're using the Expansion Board, have you removed the CTS and RTS jumpers from the board?

                  When using the expansion board with a FiPy, you will need to remove the CTS and RTS jumpers as these interfere with communication with the cellular modem.

                  https://docs.pycom.io/chapter/gettingstarted/connection/fipy.html

                  D 1 Reply Last reply Reply Quote 0
                  • D Offline
                    DDA @jmarcelino
                    last edited by

                    @jmarcelino
                    I took out the CTS and RTS jumper at the start itself, rest of the jumpers in place.
                    The unit is not responding to

                    lte=LTE()

                    its hangs up, first time it was stuck for over 3 minutes that's when I did Ctrl-C to get out of it. Tried again and its stuck again and won't respond to lte=LTE()

                    J 1 Reply Last reply Reply Quote 0
                    • J Offline
                      jmarcelino @DDA
                      last edited by

                      @dda
                      So lte = LTE() doesn't respond? Even from power up?

                      If so please open a ticket with our service desk so we can best handle it.

                      https://pycomiot.atlassian.net/servicedesk/customer/portal/1

                      D 2 Replies Last reply Reply Quote 0
                      • D Offline
                        DDA @jmarcelino
                        last edited by

                        @jmarcelino
                        Finally responding now after a few power-ups.

                        Connecting on COM25...

>>>
>>> from network import LTE
>>> lte = LTE()
>>> lte.send_at_cmd('ATI')
'\r\nERROR\r\n'
>>> lte.send_at_cmd('ATI')
'\r\nERROR\r\n'
>>> lte.send_at_cmd('ATI')
'\r\nERROR\r\n'
>>>
                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          DDA @jmarcelino
                          last edited by DDA

                          @jmarcelino
                          And on retrying the firmware upgrade again, this time I am getting a different error once and back to the same AT+SMSWBOOT failed error

                          <<< Welcome to the SQN3330 firmware updater >>>
Entering recovery mode
Resetting.

Starting STP (DO NOT DISCONNECT POWER!!!)
Traceback (most recent call last):
  File "main.py", line 2, in <module>
  File "/flash/lib/sqnsupgrade.py", line 114, in run
NameError: local variable referenced before assignment
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32
Type "help()" for more information.
>>>
<<< Welcome to the SQN3330 firmware updater >>>
Entering recovery mode
Traceback (most recent call last):
  File "main.py", line 2, in <module>
  File "/flash/lib/sqnsupgrade.py", line 98, in run
OSError: AT+SMSWBOOT=3,0 failed!
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32
Type "help()" for more information.
>>>

                          I have not done any changes to my code or file since the last error: OSError: AT+SMSWBOOT=3,0 failed!

                          1 Reply Last reply Reply Quote 0

                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                          With your input, this post could be even better 💗

                          Register Login
                          • 1 / 1
                          • First post
                            Last post

                          Pycom on Twitter

                          Pycom