The same AT+RMTXPOWER commands work sometimes but not others

IoT Modules Legacy HL Series
1

Hi,

We notice, that after freshly booting our HL7692 module (has RHL769x.2.23.172400.201706231140.x7120m_1 firmware, that it came with), often (maybe 3 times in 5), 2G AT+WMRXPOWER commands fail. On the other two boots, the exact same commands, work fine. Here’s some example commands, when they work:

AT+WMRXPOWER=1,900,62,-109
+WMRXPOWER: -84.4
OK
AT+WMRXPOWER=1,1800,699,-108
+WMRXPOWER: -85.6
OK

And here’s the same commands, when they don’t:

AT+WMRXPOWER=1,900,62,-109
ERROR
AT+WMRXPOWER=1,1800,699,-108
ERROR

Is this all a bug perhaps, with the 2.23 firmware ? A known one ? That is fixed in a later firmware version ? We see the latest presently is 2.27. The 2.27 release note makes no mention of the AT+WMRXPOWER command. But what about other firmware versions, between 2.23 and 2.27 ? They are not available on the Sierra website, nor their releases notes. So who knows ?

If a bug with 2.23 firmware, is there some workaround ? We’ve tried, prior to issuing our first AT+WMRXPOWER command, the following, none worked: 1) Issuing a AT+WMRXPOWER=0 command. 2) Issuing a AT+WMTXPOWER=0 command. 3) Issuing both. 4) Issuing an ATI command. 5) Issuing an AT command. 6) Issuing just a carriage return.

Best regards,

David

2

Hi @david.king,
I have tried your scenario on our module with FW 2.23. The issue doesn’t happen

at

OK
ati9

RHL769x.2.23.172400.201706231140.x7120m_1
HL7692
HL769x.2.23
x7120m
FUSED
2017-06-23 11:44:41
r9909

OK
at+wmrxpower=1,900,62,-109

+WMRXPOWER: -79.6

OK
at+wmrxpower=1,900,62,-109

+WMRXPOWER: -82.8

OK
at+wmrxpower=1,900,62,-109

+WMRXPOWER: -82.6

OK
at+wmrxpower=1,900,62,-109

+WMRXPOWER: -81.3

OK
at+wmrxpower=1,900,62,-109

+WMRXPOWER: -84.6

OK
at+wmrxpower=1,1800,699,-108

+WMRXPOWER: -83.4

OK
at+wmrxpower=1,1800,699,-108

+WMRXPOWER: -77.8

OK
at+wmrxpower=1,1800,699,-108

+WMRXPOWER: -81.2

OK
at+wmrxpower=1,1800,699,-108

+WMRXPOWER: -78.4

OK
Please consider upgrading your module to latest 2.27 and check again. Also keep your eyes on AT command tool. Sometimes, input AT command gets stuck and makes ERROR like your case
Let feel free to share if you have any concern. Please tick Solution if your question is answered
Thanks

1 Like
3

Hi Vianney,

Thanks for the quick try !

Just to ask, how many times did you try boot and then the sequence ? You might need to do quite a few times before you see the problem. For me about 3 in 5 times it shows the problem, but sometimes many times in a row it works fine :-/

Yes I’m happy to try 2.27, to see if makes any difference. But I would be most grateful if you could provide me first the .exe+.dwl for 2.23. Why ? So I’m able to revert my HL7692 after the check, to be the same as all our others. We don’t want to have to upgrade to 2.27 if it doesn’t help the problem :-/

Best regards,

David

4

Hi @david.king,
I tried 6-7 boot times on our module. You can download FW 2.23 and 2.27 in below link
FW 2.27:
https://source.sierrawireless.com/resources/airprime/software/hl7692-firmware-2,-d-,27/#sthash.VRGyBGYy.dpbs
FW 2.23:
https://source.sierrawireless.com/resources/airprime/software/hl7692-firmware_2,-d-,23/#sthash.9HBJoYrD.dpbs
Thanks

5

Hi Vianney,

Hmmm, I’ve tried running the 2.27 installer, but I get message per red box below. Per message, if we reboot our HL7692, nothing seems to happen. Ditto if we don’t reboot. After a minute, we see the messages below the red-boxed. And then per the last message, the prompt closes after a further 5 seconds :frowning:

x
x979×512 20.1 KB

The HL7692 is connected to my PC on COM7, comspec 115200 N81. AT command communication works fine on COM7, using a terminal emulator.

I’ve tried the installer with the HL7692 freshly booted, after waiting the 13.2 seconds for it to boot. I’ve also tried the installer after issuing a few AT commands.

I’ve googled a bit, and found this post: Dev kit HL8548-G firmware

Taking the hint cue from that post, I typed %APPDATA% in my Windows Explorer, takes me to folder C:\Users\dking\AppData\Roaming\

I then created there, an HL76xx_download.ini file, containing:

[CommPort]
Port=COM7
ComBaud=115200

Per the Dev kit HL8548-G firmware, noted that the ComBaud line might be ignored, and 115200 is used always.

Unfortunately, this guessed solution didn’t work. Ditto, if I tried instead filename HL7692_download.ini

As mentioned, our HL7692 presently has 2.23 firmware, which is what it came with. FWIW, I tried the 2.23 installer. Same sorry story.

I’m presently out of ideas !

Best regards,

David

6

Hi @david.king,
It looks like your PC which made FW installation not having FlashUSB_Driver_1_0_1_1 installed. Please refer to below link and do following steps
https://source.sierrawireless.com/resources/airprime/software/hl8548-firmware_05,-d-,05,-d-,14,-d-,0_att_zip/#sthash.qsC3vlka.dpbs

  1. Download Zip package
  2. Extract file
  3. Install FlashUSB_Driver_1_0_1_1. Ignore HL85XX firmware
  4. After driver FlashUSB_Driver_1_0_1_1 installation is completed, then you can double click FW.exe of HL7692 to upgrade via USB cable, a module reset is needed during the upgrade.
    Please share if you have any concern and tick Solution if your question is answered
    Thanks
7

Hi Vianney,

Many thanks. I’ll try that.

Is it mentioned somewhere, in some document I ought to have read ?

Meanwhile, I’ve made a bit of a discovery, by experimenting. I’ve found that the occasional ERROR response to 2G AT+RMTXPOWER commands, even though the exact same commands give OK usually, can be ‘worked around’ by preceding every 2G AT+RMTXPOWER, with AT+RMTXPOWER=0, then 20 ms wait.

I’ll see if an HL7692 firmware upgrade, from version 2.23 to 2.27, changes things at all, in this respect.

I’ve also made a discovery with the other HL7692 issue I’m seeing. You might be interested to see this thread, and in particular my most recent post:

Best regards,

David

8

Hi Vianney,

I’ve just tried your guidance for upgrading our HL7692 firmware version 2.23 to 2.27. I’m afraid the guidance didn’t work.

To get the FlashUSB driver to install, I found I needed to right-click on the C:\FlashUSB_Driver_1_0_1_1\X64\setup.exe, file, and chose Run as administrator.

Any failure of the installer leaves a file needed by the installer, locked open. A PC reboot is the workaround.

I then tried running the 2.27 installer. Namely, HL769x.2.27.183100.201809071813.x7120m_3_signed_exe.exe. But that fails as before, whether or not I reset our HL7692 when prompted. Ditto, if I reboot my PC, before installing.

I’ve arranged my PC USB cable connections, so that the HL7692 is on Port1, as below. I assume that’s what I need to do, given that the .exe says Use Port: USB1. And doesn’t seem to allow port selection, at the command line or otherwise.

x
x514×593 85.2 KB

I’ve tried running the .exe from an elevated command prompt, ditto. I’m using Win10 Version 10.0.18362.592.

Does the installer perhaps work only with a USB connection to the HL7692 ? Our HL7692 PCB has only a UART connection, via USB-to-COM adaptor. No USB connection.

If the installer works only via USB, how can we upgrade the firmware ? Over The Air upgrade might not be an option, on our production line, dependant on where in the world that line is sited, due to absence of Cellular network coverage needed for OTA.

The HL7800 firmware installer, namely HL7800.4.3.9.0_EXE, can work via UART. It provides these options: Enter Installation COM Port Type-(1.UART, 2.USB(Ymodem), 3.USB(Kermit)). We’ve twice used that installer to successfully upgrade our HL7800 module via UART.

Best regards,

David

9

Hi @david.king,
I don’t think we can use UART for upgrading firmware because flash always uses USB1. As my opinion, HL7692 is highly recommended to upgrade firmware via FOTA or USB connection. If you don’t want to use FOTA, please consider adding USB port into dev kit and try to upgrade via USB connection.
Thanks

10

Hi Vianney,

Hmmm, OTA upgrade wouldn’t be an option for us on our production lines, as it would geographically constrain production to areas of the world where there is HL7692 Cellular network coverage. In any case production line OTA upgrade would take too long and be of variable duration dependant on Cellular network conditions.

The HL7692 itself would seem to support firmware upgrade via UART as well as USB (see +BOOTDWLCFG command within AirPrime_HL76xx_AT_Commands_Interface_Guide_Rev13_0.pdf)

Might it be possible for Sierra to consider revising the HL769x.2.27.183100.201809071813.x7120m_3_signed_exe.exe installer, to support also upgrade via UART ? Perhaps Sierra could use the source code for HL7800.4.3.9.0_EXE as basis, because as mentioned, that supports upgrade via UART as well as USB.

There’s no big hurry to add HL7692 firmware upgrade via UART to the HL769x.2.27.183100.201809071813.x7120m_3_signed_exe.exe installer. But if we know you have that scheduled to be available within say, 2 months, we can plan accordingly.

The design of our daughterboard PCB that uses the HL7692, implements only UART connectivity. Adding in USB connectivity, from daughterboard to motherboard MCU, would be a major upheaval at this stage, and set back the product by several months. We were unaware that HL7692 firmware installer .exe’s were limited to USB.

Best regards,

David

11

Hi @david.king,
I got your idea but It is an existing behavior. Sorry for your inconvenience. You can raise your concern to local distributor or reseller for hardware support
+BOOTDWLCFG command just support firmware download
Please tick Solution if your question is answered
Thanks

12

Hi Vianney,

Apologies for the delay in responding further. About the HL7692 firmware V2.27 installer .exe (HL769x.2.27.183100.201809071813.x7120m_3_signed_exe): You indicated in your 10 March message, ‘I don’t think we can use UART for upgrading firmware because flash always uses USB1.’

I have some good news, and some bad news. First, the good news: Matthew Lewis, of Sierra Wireless, has been in touch. He said we can make the .exe work instead with a COM port, as follows:

1 Rename the .exe installer to .7z, and drill into with 7-Zip (yes the .exe is infact a self-installing 7-Zip file)

2 Extract all the files, and edit the entry.bat file, changing these two lines:

Before: set DL_PORT=USB1
After: set DL_PORT=COM1

Before: set DL_BAUD=460800
After: set DL_BAUD=115200

Instead of COM1, type whatever COM port you are using for your connection to the HL7692. Instead of 115200, use whatever baud rate you wish to use.

3 Change also the two lines as below, in entry.bat. Matthew didn’t mention. But I suggest, to keep any fail message on-screen, as opposed to it disappear after 5s:

Before: echo This prompt will be closed in 5 seconds
After: echo Press a key to close this prompt

Before: PING 127.0.0.1 -n 6 >nul
After: pause

4 Run the launch.bat file. Matthew didn’t mention. But I worked out. by trial-and-error, by running each of the batch files, and seeing which worked.

Same applies to the HL7692 firmware V2.23 installer .exe (HL769x.2.23.172400.201706231140.x7120m_1_signed.exe).

The bad news, is that we are finding, with 3 different HL7692 modules, the install process usually fails, bricking the module, in various different ways. Here’s a PDF, with the sorry story. HL7692 firmware installer results.pdf (616.2 KB)

We’ve burned about 3 days on trying the above technique.

We next tried 1K-Xmodem download of HL7692 firmware .dwl file (HL769x.2.27.183100.201809071813.x7120m_3_signed_dwl).

We note from page 137 of the HL7692 AT guide (AirPrime_HL76xx_AT_Commands_Interface_Guide_Rev13_0.pdf), that at boot, the HL7692 waits 150ms (fixed), for an incoming 1K-Xmodem firmware download. We’ve scripted a download using TeraTerm, to occur within 150ms of releasing the HL7692 reset line. But the download just hangs in TeraTerm, with no progress shown. We’ve tried various wait periods, 20 50 75 100 125 150 ms, but same story for each.

Do you have a TeraTerm .ttl file that works for HL7692 firmware .dwl file download ?

Best regards,

David

13

Hi @david.king,
I am successful in upgrading HL7692 via dwl using teratern. Below the steps that I did
-Download teraterm file here

  • Extract zip file then open ttermpro.exe
  • Open serial port
  • Send : AT+WDSI=4095
  • Define the size of dwl file: at+wdsd=20304768. (This number is the size of file. You can see below)
    3
    3361×506 13.2 KB
  • Select <Transfer> then <Send File>. Select rev.dwl and 1K Xmodem, then click Send. It starts transferring the file. It takes about 15 minutes to complete transfer process
    2

OK
+WDSI: 3 /// It means a package is ready to install
at+wdsc?
+WDSC: 0,0
+WDSC: 1,0
+WDSC: 2,1
+WDSC: 3,0
+WDSC: 4,15,60,240,960,2880,10080,10080

OK

  • Start install FW. When module responses WDSI:14. Teratern will be disconnected. Go set up>Serial port>Open it again

at+wdsr=4
OK

4
4819×510 6.03 KB

  • The firmware is upgraded successfully
    5
    5814×513 6.22 KB

    Please share any concerns you have. Help us tick Solution if the answers help resolve your problem
    Thanks
14

Hi Vianney,

I ran into a problem at your step as below:

Send : AT+WDSI=4095

All 3 of our HL7692 modules are presently bricked, due to failure of the Matthew Lewis technique. So are not accepting AT commands. Help !

Best regards,

David

15

Hi @david.king,
Does’n module response any? Have you tried?

  1. Turn on echo?
    ate1
  2. It maybe go to sleep mode. Let check
    at+ksleep?
    If it shows at+ksleep=1. Please change it by AT+KSLEEP=2 to disable sleep mode
    Let feel free to share any concerns. Help us tick Solution if your question is answered
    Thanks
16

Hi Vianney,

As mentioned all three of my HL7692 modules are in bricked state presently, so no AT commands of any kind are being accepted. One HL7692 occasionally can be flashed OK using the Matthew Lewis technique. But after flashing, UART transmits, we see the SIM present etc message, but won’t receive. Which is kinda wierd, as it just received 20 MB of firmware image OK. We’ve tried all with and without hardware flow control, makes no difference to observed behaviours. Help!

David

17
  • Which baudrate did you use while upgrading FW? Please open terminal by that baudrate
  • If you still cannot enter AT command on the module I am afraid that the modules was blocked when you had tried an unofficial way to upgrade FW. Please consider insert an USB port to re-upgrade. It maybe save the modules
  • If the issue still happens, please contact your reseller/distributor for more support
    Let feel free share any concern you have. Help us tick Solution if your question is answered

Thanks

18

Hi Vianney,

We used 115200 baud. About the method used to upgrade the FW, I would consider it official, as it was advised by a Sierra representative, in response to an enquiry about how to update HL7692 firmware via UART connection. Our circuit design omits USB connection to the HL7692 module. Is there some Sierra documentation that says users should always include USB connectivity within their circuit designs? Best regards, David