NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS50 stopped working
Over night the RBS50 stopped working. I tried to reset it but it did not work. After a few resets, the reset button does not work anymore. I tried the TFTP client method but my computer doesnt even recognise the ethernet cable. Now I'm read the serial port and getting this:
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00110
S - IMAGE_VARIANT_STRING=DAAAANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000023
S - Reset status Config, 0x00000033
S - Core 0 Frequency, 0 MHz
B - 262 - PBL, Start
B - 1341 - bootable_media_detect_entry, Start
B - 18701 - bootable_media_detect_success, Start
B - 18716 - elf_loader_entry, Start
B - 20928 - auth_hash_seg_entry, Start
B - 23091 - auth_hash_seg_exit, Start
B - 58143 - elf_segs_hash_verify_entry, Start
B - 172935 - PBL, End
B - 172960 - SBL1, Start
B - 265056 - pm_device_init, Start
D - 9 - pm_device_init, Delta
B - 266569 - boot_flash_init, Start
D - 29858 - boot_flash_init, Delta
B - 300781 - boot_config_data_table_init, Start
D - 13401 - boot_config_data_table_init, Delta - (419 Bytes)
B - 316799 - clock_init, Start
D - 7523 - clock_init, Delta
B - 327765 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B - 331172 - sbl1_ddr_set_params, Start
B - 336265 - cpr_init, Start
D - 2 - cpr_init, Delta
B - 340649 - Pre_DDR_clock_init, Start
D - 4 - Pre_DDR_clock_init, Delta
D - 13173 - sbl1_ddr_set_params, Delta
B - 353947 - pm_driver_init, Start
D - 2 - pm_driver_init, Delta
B - 425205 - sbl1_wait_for_ddr_training, Start
D - 27 - sbl1_wait_for_ddr_training, Delta
B - 441383 - Image Load, Start
D - 152092 - QSEE Image Loaded, Delta - (262104 Bytes)
B - 593905 - Image Load, Start
D - 899 - SEC Image Loaded, Delta - (0 Bytes)
B - 603738 - Image Load, Start
D - 213466 - APPSBL Image Loaded, Delta - (416039 Bytes)
B - 817631 - QSEE Execution, Start
D - 59 - QSEE Execution, Delta
B - 823812 - SBL1, End
D - 652965 - SBL1, Delta
S - Flash Throughput, 1807 KB/s (678738 Bytes, 375551 us)
S - DDR Frequency, 672 MHzFormat: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00110
S - IMAGE_VARIANT_STRING=DAAAANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000023
S - Reset status Config, 0x00000033
S - Core 0 Frequency, 0 MHz
B - 262 - PBL, Start
B - 1341 - bootable_media_detect_entry, Start
B - 18681 - bootable_media_detect_success, Start
B - 18695 - elf_loader_entry, Start
B - 20907 - auth_hash_seg_entry, Start
B - 23067 - auth_hash_seg_exit, Start
B - 58115 - elf_segs_hash_verify_entry, Start
B - 173366 - PBL, End
B - 173390 - SBL1, Start
B - 265485 - pm_device_init, Start
D - 9 - pm_device_init, Delta
B - 267001 - boot_flash_init, Start
D - 29963 - boot_flash_init, Delta
B - 301318 - boot_config_data_table_init, Start
D - 10822 - boot_config_data_table_init, Delta - (419 Bytes)
B - 314755 - clock_init, Start
D - 7551 - clock_init, Delta
B - 325748 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B - 329154 - sbl1_ddr_set_params, Start
B - 334247 - cpr_init, Start
D - 2 - cpr_init, Delta
B - 338630 - Pre_DDR_clock_init, Start
D - 4 - Pre_DDR_clock_init, Delta
D - 13171 - sbl1_ddr_set_params, Delta
B - 351926 - pm_driver_init, Start
D - 2 - pm_driver_init, Delta
B - 423081 - sbl1_wait_for_ddr_training, Start
D - 28 - sbl1_wait_for_ddr_training, Delta
B - 439506 - Image Load, Start
D - 148234 - QSEE Image Loaded, Delta - (262104 Bytes)
B - 588168 - Image Load, Start
D - 899 - SEC Image Loaded, Delta - (0 Bytes)
B - 598000 - Image Load, Start
B - 614984 - Boot error ocuured!. Error code: 303a
Is there another option to upload or reset the satellite or is it e-waste?
Thanks for any tips and help
4 Replies
Using TFTP (or nmrpflash: https://github.com/jclehner/nmrpflash
depends on making connection to the correct IP address.
After a Factory Reset, the original RBR50 router defined 192.168.1.1 as the IP address when booting up, and the RBS50 satellite defined 192.168.1.250 for the IP address .
(when the AX products were introduced, Netgear changed the IP address. Ralph Waldo Emerson: "a foolish consistency is the hobgoblin of little minds." No one will ever accuse Netgear of consistency.)
So if the computer running TFTP is trying to connect to 192.168.1.1, there is nothing there.
Using TFTP is not a trivial exercise. (not nearly as ambitious as connecting to the serial port, but still "out of the ordinary"). I have used TFTP on a number of occasions with an RBR50 and on one attempt had failed five times in a row. "well, time to get out the hammer and beat this into tiny pieces. Oh, what the heck, why not try it a couple more times." On try six, it worked!
My feeling is that TFTP is really sensitive to timing. a second too early, and it fails. a second too late, and it fails.
And, yes, it could be e-waste.
Can try a 30-30-30 reset on the RBS, if this fails to bring back the RBS to normal operation, then needs to be replaced.
Thank you for your suggestions, I tried the 30-30-30 but apart from solid green for power nothing else is lighting up, so into the trash with the whole system :(
If the RBR is working, you could get another RBS. You can find then still out in the wild.
