Unable to flash RBS850 in boot loop

[tnine]

Hello,
I've recently downloaded, compiled, and installed version e181f92 in an attempt to flash an RBS850 that seems to be continually stuck on a boot cycle. The RBS850 does boot, I can even load the admin UI on 192.168.1.250. However, shortly after starting the service, the firmware seems to error and the unit reboots.

I've attempted to flash the unit with the following command.

sudo nmrpflash -vvv -i en5 -f ~/Downloads/RBS850-V4.6.3.16/RBS850-V4.6.3.16-signed.chk  -t 180000 -A 192.168.1.2 -M 255.255.255.0 -a 192.168.1.250 -m 6C:CD:D6:2D:72:6C

This renders the output below. Note the sendto error seems to occur when the unit reboots itself.

Waiting for Ethernet connection.
Adding 192.168.1.2 to interface en5.
Advertising NMRP server on en5 ... -
delete: cannot locate 192.168.1.250
Received configuration request from 6c:cd:d6:2d:72:6c.
Sending configuration: 192.168.1.250/24.
Received upload request: filename 'firmware'.
Using remote filename 'firmware'.
Uploading RBS850-V4.6.3.16-signed.chk ... << WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
sendto: Can't assign requested address
192.168.1.250 (192.168.1.250) deleted

If I remove the IP ranges for my interface, and the RBS's interface and keep the MAC address, I get the following output.

sudo nmrpflash -vvv -i en5 -f ~/Downloads/RBS850-V4.6.3.16/RBS850-V4.6.3.16-signed.chk  -t 180000  -m 6C:CD:D6:2D:72:6C

Waiting for Ethernet connection.
Adding 10.164.183.253 to interface en5.
Advertising NMRP server on en5 ... -
delete: cannot locate 10.164.183.252
Received configuration request from 6c:cd:d6:2d:72:6c.
Sending configuration: 10.164.183.252/24.
Received upload request: filename 'firmware'.
Using remote filename 'firmware'.
Uploading RBS850-V4.6.3.16-signed.chk ... << WRQ(firmware, octet)
Uploading RBS850-V4.6.3.16-signed.chk ... << WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
<< WRQ(firmware, octet)
Timeout while waiting for ACK(0)/OACK.
10.164.183.252 (10.164.183.252) deleted

During the time nmrpflash is uploading the firmware, the unit seems to be stuck in the continuous boot loop, which occurs about every 1:08. Any ideas on how to proceed?

Note that when the message Received configuration request from 6c:cd:d6:2d:72:6c. the LED power light on the back turns amber, and it appears to stay that color for around 5 seconds, then it turns green. It seems like the request for upload is received, but the unit won't stay on long enough to transmit the firmware.

Thanks in advance!
Todd

[jclehner]

First off, sorry for the late answer. From your description I gather that the device reboots every 1:08, regardless of whether it's in NMRP mode or a normal boot? In that case, it's more likely to be a hardware issue (maybe causing a watchdog reset?).