Hello,
I’m trying to revert the firmware of the TRB500 from TRB5_R_00.07.04.5 to TRB5_R_00.07.03.1. However using the firmware image available at TRB500 Firmware Downloads - Teltonika Networks Wiki , the modem indicates the error: Invalid image an unexpected error occured and refuse to use the older image.
Is there a reason why the downgrade is not possible or is there another place to get a valid image?
Best regards,
Joachim
Hello,
There are no artificial limitations on firmware downgrade, so I’d like to dive deeper into what the issue could be. I will ask you to run the following commands using the SSH or CLI:
wget https://wiki.teltonika-networks.com/images/e/e0/TRB5_R_00.07.03.1_WEBUI.bin -P /tmp
sysupgrade /tmp/TRB5_R_00.07.03.1_WEBUI.bin
And check if any errors appear in the logs, or if the downgrade if successful. The provided commands download the firmware .bin file to the volatile memory, and perform the sysupgrade command, that is also used by the WebUI for the update process.
If the update fails, please attach the output of these commands in your next comment.
Best regards,
Hello,
sorry for the delay, I didn’t had access to the modem the past week.
Here is the output in the terminal:
root@TRB500:~# sysupgrade /tmp/TRB5_R_00.07.03.1_WEBUI.bin
Mon Oct 2 09:07:26 CEST 2023 upgrade: TRB5_R_00.07.03.1
Mods found: Embargo module detected, but fw does not support it
This firmware is unsupported by hardware
Image check failed.
I don’t know if this is related, but on TRB5 Firmware checksum list - Teltonika Networks Wiki it seems that the SHA256 checksum for the TRB5_R_00.07.03.1 and TRB5_R_00.07.03.2 are inverted (the MD5 checksum are correct)
Hello,
As the error suggest, your hardware does not support downgrading of firmware. I will ask you to navigate to System → Firmware → Update firmware, and upload a screenshot of CURRENT FIRMWARE INFORMATION section, as well as Batch number with Hardware revision from the Status → System menu. Thank you.
Additionally, could you clarify why you’d like to revert to this firmware version?
Best regards,
Hello,
this is the firmware information:
I want to revert the firmware because another TRB500 was working in January on a test 5G SA cell, but now, after deployment of a similar cell (100MHz TDD on band N78), the modem disconnects after a few seconds. Therefore, I first wanted to first check if it was a firmware issue or potentially a problem of the cell configuration.
Thank you for the information!
To better understand the issue of the device not connecting, I’ll ask you to replicate the issue, then navigate to System → Administration → Troubleshooting, open the System Log, and copy the logs from the last few minutes. These logs can be pasted in your next comment, or if you encounter character limit issues, please upload the logs to a third-party hosting service. Make sure you remove any sensitive information!
Perhaps any logs are available from the gNodeB or the Core network that would help narrow down the issue?
Additionally, after replicating the issue, please log into the CLI/SSH of the device, and run the following command:
gsmctl -A 'AT+CEER'
The output of this command could provide the reason of rejection from the network if the issue is coming from the network.
Lastly, make sure the Auto APN feature is disabled and APN is entered manually. This can be done by navigating to Network → Interfaces → General. editing the mob1s1a1 interface, and after disabling the Auto APN option entering the custom APN used in the network.
Best regards,
As for the firmware downgrade, the internal modem uses a different configuration from batch 009, and downgrade to versions earlier than TRB5_R_00.07.04.4 will not be possible, since earlier firmware releases do not contain the necessary files for communication with the modem.
A note has been added to the downloads page on our Wiki:
https://wiki.teltonika-networks.com/view/TRB500_Firmware_Downloads
Best regards,
Hello,
I’ve reproduced the error and the ‘AT+CEER’ command returns: +CEER: No cause information available.
The output of the system.log is the following after setting the connection type to “5G only”, setting the APN by hand, and rebooting the modem:
Tue Oct 3 11:22:57 2023 daemon.info mobifd: [gsm.modem0] Attempting to establish connection to operator with 60 seconds of timeout
Tue Oct 3 11:23:00 2023 daemon.err uhttpd[2159]: Command failed: Method not found
Tue Oct 3 11:23:37 2023 daemon.info mobifd: [gsm.modem0] Connected to operator ‘XXXXXX’
Tue Oct 3 11:23:37 2023 daemon.err mobifd: [gsm.modem0] Failed to get serving cell info
Tue Oct 3 11:23:37 2023 daemon.info mobifd: [gsm.modem0] -CFUN- Functionality: “Full”
Tue Oct 3 11:23:37 2023 daemon.info mobifd: [gsm.modem0] -COPS- Mode: “Auto”, operator: “XXXXXX”
Tue Oct 3 11:23:37 2023 daemon.info mobifd: [gsm.modem0] -CREG- Mode: “Enabled (with location information)”, status: “Not registered”, LAC: “”, cell ID: “”, technology: “Unknown”
Tue Oct 3 11:23:37 2023 daemon.info mobifd: [gsm.modem0] -CGREG- Mode: “Enabled (with location information)”, status: “Not registered”, LAC: “”, cell ID: “”, technology: “Unknown”
Tue Oct 3 11:23:37 2023 daemon.info mobifd: [gsm.modem0] -CEREG- Mode: “Enabled (with location information)”, status: “Not registered”, LAC: “”, cell ID: “”, technology: “Unknown”
Tue Oct 3 11:23:37 2023 daemon.err mobifd: [gsm.modem0] Failed to get IP address from PDP context “1”
Tue Oct 3 11:23:40 2023 daemon.err mobifd: [gsm.modem0] Failed to get IP address from PDP context “1”
Tue Oct 3 11:23:43 2023 daemon.err mobifd: [gsm.modem0] Failed to get IP address from PDP context “1”
Tue Oct 3 11:23:46 2023 daemon.err mobifd: [gsm.modem0] Failed to get IP address from PDP context “1”
Tue Oct 3 11:23:48 2023 daemon.err uhttpd[2159]: Failed to parse message data
Tue Oct 3 11:23:48 2023 daemon.err uhttpd[2159]: Command failed: Method not found
Tue Oct 3 11:23:49 2023 daemon.err mobifd: [gsm.modem0] Failed to get IP address from PDP context “1”
Tue Oct 3 11:23:52 2023 daemon.info mobifd: [gsm.modem0] Modem is attached to PS
---------- The following part continuously repeats itself -----------
Tue Oct 3 11:23:52 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is setting up now
Tue Oct 3 11:23:52 2023 daemon.notice netifd: mob1s1a1 (7763): wwan[7763] Searching for a valid wwan usb device…
Tue Oct 3 11:23:52 2023 daemon.notice netifd: mob1s1a1 (7763): wwan[7763] Using wwan usb device on bus
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Starting network mob1s1a1 using APN: internet
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Profile successfully modified.
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Successfully opened the port
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): [/dev/cdc-wdm0] Successfully set data format
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): QoS flow header: no
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Link layer protocol: ‘raw-ip’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Uplink data aggregation protocol: ‘qmapv5’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Downlink data aggregation protocol: ‘qmapv5’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): NDP signature: ‘0’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Downlink data aggregation max datagrams: ‘32’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Downlink data aggregation max size: ‘63’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): cid4: 14
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): [/dev/cdc-wdm0] Client ID not released:
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Service: ‘wds’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): CID: ‘14’
Tue Oct 3 11:23:53 2023 user.notice mobile.sh: error: couldn’t start network: QMI protocol error (14): ‘CallFailed’ call end reason (3): generic-no-service verbose call end reason (3,2001): [cm] no-service [/dev/cdc-wdm0] Client ID not released: Service: ‘wds’ CID: ‘14’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): pdh4:
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Unable to connect IPv4
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): No IPV4 data link!
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): error: couldn’t get current settings: QMI protocol error (15): ‘OutOfCall’
Tue Oct 3 11:23:53 2023 daemon.notice netifd: mob1s1a1 (7763): Failed to create IPV4 connection
Tue Oct 3 11:24:03 2023 daemon.notice netifd: mob1s1a1 (7997): Stopping network mob1s1a1
Tue Oct 3 11:24:04 2023 daemon.notice netifd: mob1s1a1 (7997): Command failed: Not found
Tue Oct 3 11:24:04 2023 daemon.notice netifd: mob1s1a1 (7997): Command failed: Not found
Tue Oct 3 11:24:04 2023 daemon.notice netifd: mob1s1a1 (7997): Command failed: Permission denied
Tue Oct 3 11:24:04 2023 daemon.notice netifd: Interface ‘mob1s1a1’ is now down
.---------------------------------
Hello,
All that I can see from the logs, is that the device registers on the cell, but does not receive an IP address. If you are certain that the issue is not coming from the network side, or an incorrect APN, please contact us by filling out the Contact Us form here: Teltonika Networks - LTE Routers, Gateways & Modems for IoT and our sales managers will help us establish a private communication channel to further diagnose the issue. Make sure to mention this query when writing an email. Thank you!
Best regards,
Thanks for all the information!
This topic was automatically closed after 15 days. New replies are no longer allowed.