when updating the FW, I think it was 3.5.6 to 3.5.6 - we loost the epmp-SM.
so, we removed it, connected the cable and we see that Uboot doesn’t boot.
a few days earlier - this SM was updated from version 2.0 - everything went well.
As far as I understand, the SM cannot be restored without additional equipment.
but I can’t do anything yet, the SM is 10000 km. from me.
delivery is more expensive than SM.
I looked at a similar point, AP, where is the GPS. U-boot can’t dead in this case.
can anyone come across a repair, what is the reason for this freeze?
I am afraid that this HALT will happen again on other SM ((
U-boot SMPX
DRAM:
sri
Wasp 1.3
wasp_ddr_initial_config(276): Wasp (16bit) ddr1 init
wasp_ddr_initial_config(426): Wasp ddr init done
Tap value selected = 0x8 [0xaa55aa55 - 0x0]
Setting 0xb8116290 to 0x10202d0f
4 MB
Top of RAM usable for U-Boot at: 80400000
Reserving 204k for U-Boot at: 803cc000
Reserving 192k for malloc() at: 8039c000
Reserving 44 Bytes for Board Info at: 8039bfd4
Reserving 36 Bytes for Global Data at: 8039bfb0
Reserving 128k for boot params() at: 8037bfb0
Stack Pointer at: 8037bf98
., and HALT here, no load to RAM and no uboot console. ethernet also dead.
one more question afterwards.
I worked with different equipment, and I know that
… for example for the PTP 820C, there were utilities -
to check the remaining flash memory resource.
is there nothing similar for ePMP?
thanks.
You say you were updating from 3.5.6 to 3.56? Is that a typo as it makes no sense unless you are talking about an AP and updating both banks You note that you previously updated from 2.0. You can’t go directly from 2.0 to 3.5.6, you have to go to 2.6 (if I remember correctly) and then to 3.5.6
yes, that’s right, 8 Mb flash in SM , so no sense to flash in twice.
but as far as I know, a colleague just re-uploaded the same firmware. like for AP.
as far as I understand, in the board remained uboot from v3.5
U-Boot 9344_PX 1.1.4.e (Aug 21 2017 - 16:36:48)
although in 3.5.6 it is already come with:
U-Boot 9344_PX 1.1.4.e (Feb 20 2019 - 10:30:35)
probably uboot it was not updated, because of the same version.
but when you update 3.5.6 to 3.5.6 again, something happened and now uboot halted.
of course an unofficial upgrade from 2.0 to 3.5.6 was used, using intermediate versions from google.
I haven’t seen the official migration plan, as well as firmware - on the support.
I just mentioned that a few days earlier there was a successful update, from 2.0 to 3.5.6.
no any halt or error.
that’s why I can’t understand the reason for this halt.
from 2.0 to 3.5.6 is not a good step, you needed to go to 2.4 then 2.6 then 3.1 then 3.5.6. This is well documented by Cambium and has not been hidden.
Hold the reset button in, then power on the radio with no ethernet connections just power attached, wait 30 seconds then release. plug in laptop and use 192.168.0.2 to access the radio with telnet. use the telnet commands to upload the old firmware back into the radio and issue the reboot command. let it reboot and you should have we access again, upgrade as per above. if you do not have access to the telnet, use the tftp method and pray it boots else you have a paperweight.