Hi
One of my RBS50 satellites won't connect to the router, and I have not been able to reset it or download new firmware to it in any way. Tried TFTP and nmrpflash to no avail.
So I found out about the console and got lot of info. It looks like it is booting all the way and starts up as expected.
BUT, there are a few things in the log that looks strange, and that I think might be the cause.
I'll just take in the order it popped up in the console log. The whole log is attached as a file
Here's some parts I wonder about
Is there something wrong with the NAND? ANything I can do to fix that?
I guess this explains why I was unable to download new firmware.
Any ideas why the nmrp server stopped or failed, and how to fix it?
Why does it say OpenWRT? Is Netgears firmware based on OpenWRT, or did someone change the firmware on this unit to OpenWRT? Because I sure did not! It is a second hand unit, but it has worked in my system.Still doesn't explain the other issues above I guess.
Other than the above I have not read through the whole log, excep at the end I noticed this, where it seems it is trying to connect, I assume the backhaule connection to the RBR50 router.
The unit does not connect to the router wirelessly. If I connect with cable, it will show upp as 5G connected with good backhaul status, but it won't connect. It shows IP 192.168.1.250. Which it shouldn't. I can't go it's webpage. It will respond to ping. Same thing if I connect directly to a PC.
Any ideas on how to fix this unit would be much appreciated!
One of my RBS50 satellites won't connect to the router, and I have not been able to reset it or download new firmware to it in any way. Tried TFTP and nmrpflash to no avail.
So I found out about the console and got lot of info. It looks like it is booting all the way and starts up as expected.
BUT, there are a few things in the log that looks strange, and that I think might be the cause.
I'll just take in the order it popped up in the console log. The whole log is attached as a file
Here's some parts I wonder about
Code:
U-Boot 2012.07 [Barrier Breaker unknown,unknown] (Jan 04 2017 - 13:54:09)
U-boot dni1 V1.4 for DNI HW ID: 29765352; NOR flash 32MB; EMMC flash 4000MB; RAM 512MB
smem ram ptable found: ver: 1 len: 3
DRAM: 512 MiB
machid : 0x8010001
NAND: ID = 0
Vendor = 0
Device = 0
Nand Flash error. Status = 64
ONFI Read id cmd failed
ONFI probe failed
SF NAND unsupported id:ff:ff:ff:ffSF: Unsupported manufacturer ff
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
0 MiB
MMC: qca_mmc: 0
*** Warning - bad CRC, using default environment
Is there something wrong with the NAND? ANything I can do to fix that?
Code:
Hit any key to stop autoboot: 2 1 0
eth0 PHY0 Down Speed :10 Half duplex
eth0 PHY1 Down Speed :10 Half duplex
eth0 PHY2 Down Speed :10 Half duplex
eth0 PHY3 Down Speed :10 Half duplex
eth0 PHY4 Down Speed :10 Half duplex
nmrp server is stopped or failed !
Read BootPart from BOARD DATA...
mmc_read will run command: mmc read 0x871cfca8 0x2a22 0x100
MMC read: dev # 0, block # 10786, count 256 ... 256 blocks read: OK
boot partition : 2
BootPart = 2
Loading DNI firmware for checking...
I guess this explains why I was unable to download new firmware.
Any ideas why the nmrp server stopped or failed, and how to fix it?
Code:
** rootfs address : 0x8433ffc0 **
## Checking Image at 84000000 ...
FIT image found
FIT description: ARM OpenWrt FIT (Flattened Image Tree)
Image 0 (kernel@1)
Description: ARM OpenWrt Linux-3.14.77
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x840000e4
Data Size: 3056369 Bytes = 2.9 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80208000
Entry Point: 0x80208000
Hash algo: crc32
Hash value: 3b968961
Hash algo: sha1
Hash value: dd1dda144175330a6fe1708fd8e9b9b00ada4fa9
Image 1 (fdt@1)
Description: ARM OpenWrt qcom-ipq40xx-ap.dkxx_cc device tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x842ea51c
Data Size: 39067 Bytes = 38.2 KiB
Architecture: ARM
Hash algo: crc32
Hash value: f94716db
Hash algo: sha1
Hash value: 7e37e5ed95940f74e51add9aab58a3766e853729
Image 2 (fdt@2)
Why does it say OpenWRT? Is Netgears firmware based on OpenWRT, or did someone change the firmware on this unit to OpenWRT? Because I sure did not! It is a second hand unit, but it has worked in my system.Still doesn't explain the other issues above I guess.
Other than the above I have not read through the whole log, excep at the end I noticed this, where it seems it is trying to connect, I assume the backhaule connection to the RBR50 router.
Code:
The sshenable is running ...
Sending discover...
Sending SCAN START cmd
Sending discover...
not restart eth_handle when /tmp/disable_satelite_dhcpd existed
send_vdev_down_cmd_non_tlv for vap 3 (de05c000)
Sending SCAN START cmd
Cannot connect to server , will try 60s later!!Sending discover...
Sending discover...
Sending discover...
send_vdev_down_cmd_non_tlv for vap 3 (de05c000)
not restart eth_handle when /tmp/disable_satelite_dhcpd existed
Sending SCAN START cmd
send_vdev_down_cmd_non_tlv for vap 3 (de05c000)
Sending discover...
Sending discover...
Sending SCAN START cmd
The unit does not connect to the router wirelessly. If I connect with cable, it will show upp as 5G connected with good backhaul status, but it won't connect. It shows IP 192.168.1.250. Which it shouldn't. I can't go it's webpage. It will respond to ping. Same thing if I connect directly to a PC.
Any ideas on how to fix this unit would be much appreciated!