RG500Q Booting issue

Hi,

We have one of the boards that has an RG500Q module. Recently, we’ve been encountering the following issue:

  • It does not boot and is not recognized in the device manager.
  • However, when we switch to emergency flash mode, it shows the port, and we are able to flash it. After switching back to normal mode, the same problem arises as it is not detected in the device manager.
  • when we connect to the Debug Port to check the boot logs using Tera Term software,

The logs appear as follows:

Platform Init [ 1594] BDS
UEFI Ver : 5.0.210122.BOOT.UEFI.4.0-00195-SDX55LEZB-2
Platform : MTP
Subtype : 5
Chip Name : SDX55
Chip Ver : 2.0
Core 0 Freq: 1497 MHz

UEFI Total : 227 ms
POST Time [ 1596] OS Loader
Loader Build Info: Jun 30 2021 05:05:36
VB: RWDeviceState: Succeed using devinfo!
Total DDR Size: 0x0000000020000000
BootMode:0, BootReason:0
Fastboot=0, Recovery:0
GetVmData: No Vm data present! Status = (0x80000003)
VM Hyp calls not present
Fastboot command: fastboot-abnormal
Launching fastboot
Fastboot Build Info: Jun 30 2021 05:05:32
hsusb_phy_init_success: 0
ssusb_phy_init_success: 0
Fastboot: Initializing…
Partition not found : frp
Error Reading FRP partition: Not Found
Fastboot: Processing commands
Failed to get the graphics output protocol.
Failed to get the graphics output protocol.
Failed to get width or height
Failed to get the graphics output protocol.
Failed to get the graphics output protocol.
Unable to show fastboot menu on screen: Out of Resources
UsbfnDwcCoreCableStatus: PmicSmbchgProtocol->ChargerPort() failed with error: Unsupported. Assume SDP
Dev_Common_Speed: Bus Speed: High
Bulk in XFR aborted
Error, should not happen! Check your USB connectionDev_Common_Speed: Bus Speed: High

Could you please suggest any solutions?

Dear @Pavan
Could you share your current firmware? And which series did you use?RG500Q-EU or others?

Dear @Pavan
Could you try to execute "fastboot reboot "?

Dear @silvia

Thank you for your response.
When we tried on a Windows OS, it showed “ADB Devices not found.” However, after we switched to a Linux OS, we were able to execute “fastboot reboot,” and now the module is working fine.