Wrong firmware on RAK7268V2

LPWAN Industrial Gateways / Concentrators
1

I have tried to recover the firmware on the RAK7268V2 Lite that I received and have managed to program it with an older version of the WisGateOS using a recovery process I found.

It boots but I get an error message “jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00e20024: 0x5e67 instead” and a kernel panic at the end of the boot sequence.

How can I restore the latest version of the WisGateOS2?

Thanks in advance for any and all assistance.

2

Hello Mike,

Which version is that?
What problem made you recover, not just reflash with the latest version?

Regards,
Nikola Semov

3

Hi,

Thanks for the comment.

I am documenting what I did so that others can find this as needed.

I wanted to try the chirpstack update on this gateway, but it did not work. That left me with a bricked 7268V2 with no ability to get back to WisGateOSV2.

What I ended up doing…

  • Used the recovery procedure to get WisgateOS recovered via tftpbooot. I had to set up a tftpboot server on my Mac to source the files. I had to connect to the console of the gateway via usb-c to tell the gateway to do a tftp boot sequence.

  • I also had to set the IP address of my Mac to match that suggested by the gateway via the tftp process.

  • This got the gateway recovered to V1 but with no visible option to do the update to WisGateOSV2 via the WisDM tool or via the web UI on the gateway.

  • Once I had installed the WisgateOS V1, it seems to have hosed up the file system on the gateway and I could not install the “latest” V2 version via tftp, as it gave me the memory error above.

  • I located the first version of WisGateOSV2, release 2.01 and tried to install via ftfp. That worked and seems to have run a process to reformat and repair the filesystem error (like fsck?).

  • I was then able to use the WebUI to update the WisGateOSV2 version to the latest as the V2.01 release had the ability to do updates via the WebUI. I downloaded the latest and pointed the WebUI to that file on my computer to update.

Nowhere is any of this documented on the support website or in documentation.

But, I have the gateway up and running. So all good and I know what to do to try the Chirpstack firmware at some point in the future and recover.

Hopefully this will help someone else that wanders down this path…

4

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.