Just followed this guide to update my device- I had success on first attempt (MKR NB 1500).
Notes on my attempt:
I also did not need to do the pin bridging, switch connection, or pin grounding (see #15 by @leehelzer)
I followed the steps in #2 exactly, except I did not add the switch or modify the SerialSARAPassThrough sketch. For step 7, I just disconnected the SARA USB cable. For step 8, I simply reconnected the cable.
I did not need to run any program in Administrator mode.
Here is the log from my install, for posterity:
Using USB port
Processing 'SARA-R410M-02B-03-L0.0.00.00.05.12_A.02.19_IP.dof'
Please TURN ON the device and don't disconnect power supply
Waiting for device...
Device found!
Mobile Version report: PASS
Ext Mobile Mobile SW Rev: L0.0.00.00.05.08
-> Backup of legacy NV objects
Process time was 9.0 sec.
OK
-> Backup of ublox legacy NV objects
Process time was 47 msec.
OK
-> Backup of RF NV objects
Process time was 3.4 sec.
OK
-> Backup of CONF NV objects
Process time was 2718 msec.
OK
-> Backup of FS objects
Process time was 0 msec.
OK
-> Backup of Alternate FS objects
Process time was 0 msec.
OK
-> Switching to download mode
Waiting for synchronization...
<1>
Device synchronized.
Injecting NPRG9x06.mbn
Boot-loader is active
-> Partition table '0:MIBIB' from 'partition.mbn' loaded!
Process time was 6.0 sec.
OK
-> Start downloading item '0:EFS2' from 'efs.mbn'
Process time was 2312 msec.
OK
-> Start downloading item '0:sec' from 'sec.dat'
Process time was 16 msec.
OK
-> Start downloading item '0:TZ' from 'tz.mbn'
Process time was 984 msec.
OK
-> Start downloading item '0:MBA' from 'mba.mbn'
Process time was 454 msec.
OK
-> Start downloading item '0:ACDB' from 'acdb.mbn'
Process time was 234 msec.
OK
-> Start downloading item '0:RPM' from 'rpm.mbn'
Process time was 281 msec.
OK
-> Start downloading item '0:QDSP' from 'qdsp6sw.mbn'
Process time was 41.9 sec.
OK
-> Start downloading item '0:APPS' from 'apps.mbn'
Process time was 8.4 sec.
OK
-> Start downloading item '0:UA' from 'UA9x06.mbn'
Process time was 343 msec.
OK
-> Start downloading item '0:EFS2BKUP' from 'padded_efs.mbn'
Process time was 1750 msec.
OK
-> Start downloading item '0:EFS2APPSBKUP' from 'efs2.mbn'
Process time was 547 msec.
OK
-> Start downloading item '0:EFS2APPS' from 'efs2.mbn'
Process time was 563 msec.
OK
-> Start downloading item '0:SBL' from 'sbl1.mbn'
Process time was 406 msec.
OK
Resetting device...
Device found!
-> Restore of legacy NV objects
Process time was 234 msec.
OK
-> Restore of ublox legacy NV objects
Process time was 62 msec.
OK
-> Restore of RF NV objects
Process time was 6.0 sec.
OK
-> Restore of CONF NV objects
Process time was 1891 msec.
OK
-> Restore of persistent objects in FS
Process time was 0 msec.
OK
-> Restore of persistent objects in Alternate FS
Process time was 0 msec.
OK
-> Apply SCR objects
Process time was 15 msec.
OK
Mobile Version report: PASS
Ext Mobile Mobile SW Rev: L0.0.00.00.05.12
Extra command: RESET
Process time was 0 msec.
OK
Process time was 1 min 43 sec.
Done!
Please TURN OFF the device and press 'Start' to install the firmware
Thank you to everyone for their contributions to this thread. I have been trying to get my MKR NB 1500 to connect to AWS for over a year (off and on) and this finally fixed the issue. Upgraded the modem firmware and it finally connected to AWS!
Hi everyone,
could someone kindly share the SARA-R410M-02B-03-L0.0.00.00.05.12_A2.19_IP.zip file or show me where to download it? The u-blox support asked me to write in forums, ecc......
Current firmware is L0.0.00.00.05.08 and I'm able to connect in https to arduino.cc but in some site the https connection fails... despite I have uploaded the root certificate of these sites...
I hope this firmware version solves these issues otherwise I will have to change the hardware.
Thanks
Giuseppe
It's over 20 mb and thus not sendable here. Also it's not clear if it's legal to spread the software. Check #15 and solve the maze...you can find a hint under MKR NB 1500 stuck in + CEREG: 0.0 - #12 by intstarep#13
So what's the best plan of attack if we've followed all of this, upgraded the firmware, and still have no luck sending nor receiving a single SMS? I've downgraded the SAMD firmware to 1.8.9 that I've seen mentioned here just incase that could help, but nothing. My modem and now updated firmware works fine with the SARA passthrough examples, NTP time retrieve example, RAT configuration example, etc. and also gets basic info from u-blox's m-center. It will "send successfully" an SMS through m-center but my phone never receives anything. I'll send it a text on my phone and it will never receive anything in m-center. As a side note, in the Arduino MKR NB's RAT Config example, it sets the LTE-M network "successfully" but issuing the same commands from AT Console in m-center, such as "AT+URAT=7" doesn't get any kind of response.
Are there any AT commands I can try that might clue me in on whether to call AT&T, or call u-Blox?
You are right. The RAT config example does not work anymore, i just report a issue on github.
Initialize the sms sketch with NB nbAccess(true); and copy the serial monitor output and paste it here.
PS1: Calling At&T or ublox with this problem is IMHO just wasted time, they can't help you.
In this thread, it is mentioned that there may be issues in the R410M's firmware that cause it to hang up after a while. I upgraded the firmware according to the above and while I haven't figured out the exact time threshold, it seems to go into a sleep state of some kind after roughly 1.5 to 2 hours. I then sent it a text message and it replied about 45 minutes later, at which point all text message attempts following that moment were responded to pretty instantly. The above thread also mentions AT&T being the possible culprit.
Should executing
AT+CPSMS=0
AT+CFUN=15
resolve this issue? Think maybe what they're considering unresponsive is just an AT&T PSM network assignment?
No one here asks about the qualcomm drivers. I have the MIKROE-3072 and I'm missing the Qualcomm drivers. I contacted Qualcomm but they don't "offer support or drivers to end consumers". I contacted MIKROE and they claim that drivers download automatically through Windows Device Manager (they don't). There are plenty of malware links online that claim to be the drivers. Tried some though, but no luck. So, can someone point me in the right direction? Thank you.
Thanks a lot!
Since you mentioned already that you also have the Mikroe modem, do you, by any chance, know how to pass data from/to the UART pins. I have to connect Mikroe to another board and Mikroe works as the intermediate in the communication.
Hi,
My MKR 1500 seems to be into cyclic abort and reboot during installing the upgrade. Is there anyway I can reset the modem and restart the process ?
I installed SerialSARAPassthrough, soldered the SARA USB 4 pins, and got the Qualcomm modem up with 2 devices in linux :
ttyUSB0 that is sending 'Feb 03 201813:00:41Feb 03 201813:00:419607.' on boot, but no AT contact. Looks like part of the software version.
ttyUSB1 responds to AT commands.
So I uploaded the software with minicom/xmodem with AT-command, but ended up with cyclic rebooot. Notice the messages in norwegian from minicom that signals lost connection.
Hi
As zbelding wrote, the good'old xmodem times are over for weak reasons.
So, it seems (two bad news): You need to solder the board and to use a windows pc...
