AR-300m upgrade uboot to newer verions

tortue · 2017-11-02T15:54:19.000Z

I have the newer uboot on my AR300M but the switch is not forcing a boot to a specific flash after setting the boot_dev variable. How can I erase the uboot env variables to see if that will fix it for me also? Is there a specific one I could clear that might do it?

I don’t have a UART connector capability so would need to do this from either the NAND or NOR booted systems.

Thanks

dlakelan · 2017-11-16T04:27:36.000Z

I have this router purchased Nov 2017, flashed the latest 2.263 NAND firmware via the GUI, I then flashed the LEDE 14.01.4 NOR firmware via UBOOT web update. Now I want to be able to boot the NOR image by using the switch.

What is the current procedure? What is the latest tested working uboot image? I have no UART adapter at the moment, is it possible to flash new uboot via a web gui?

dlakelan · 2017-11-16T14:10:56.000Z

using uboot web interface I flashed LEDE to the NOR firmware, and then also using uboot web interface flashed the above linked new uboot: 404 Page not found - GL.iNet

Now my system boots only to NOR, which is actually very good for me because I wanted the LEDE firmware, however it apparently doesn’t boot to the NAND firmware anymore, regardless of which way I set the switch. Yes I have set boot_dev on

How can I now use the switch for selecting NOR vs NAND?

alzhao · 2017-11-16T14:47:27.000Z

You have to use USB UART adapter and connect to the serial pins.

You can try flash the nand firmware again using the uboot console.

fleskalebas · 2017-11-27T16:58:00.000Z

Just a little tip:

When you flash custom firmware and the routers doesn’t boot AND you don’t want to solder (I want to keep the case around the board). Just execute this little trick to trigger bootcount:

Insert power, wait until the first flash of the led (after 2 seconds), and disconnect the power cord (bootcount =1)
Repeat (bootcount=2)
Repeat (bootcount=3)
Now you can insert the power cord and keep it inserted, it now boots the NOR flash

Easier than logging in and setting bootcount=4.

sportfreund · 2017-12-23T17:40:14.000Z

Hi, I think i bricked my AR300M. I flashed the new Uboot via web console but the switch still did not work. So as alzhao described I cleaned all env parameters (all means all, i cleaned ipaddr, dlf, blf, everything).

Now even the Unbrick method via 192.168.1.1 doesn’t work anymore. The device still seems to be alive, though, the LEDs still blink at startup. But even via UART I only get unreadable letters, no matter what baud rate I choose.

m.vgunten · 2018-07-16T09:01:07.199Z

Hi to all.

I also flashed the latest U-Boot from https://github.com/gl-inet/gl-uboot-source-for–ar300m to my AR300M (using prebuilt in bin / MD5 2d34d88fd33fa9128afc1d51269ee9c7).

U-Boot 1.1.4-g36de7573 (May 26 2017 - 14:42:18)

Then erased all environment vars using
erase 0x9f040000 +0x10000
reset

both
run bootcmd
and
run blf
boot correctly into NAND and NOR firmware respectively.

But during normal startup / reset I always get the following error:
Device 0 bad blocks:
07fc0000
07fe0000
Found ART,Checking calibration status...
Device have calibrated,Checking device test status...
Device haven't tested. Please test device in calibration firmware...
Booting image at: 0x9Fed0000
## Booting image at 9fed0000 ...
Bad Magic Number

Any help is appreciated!
Thanks Martin

alzhao · 2018-07-17T01:36:43.145Z

Can you make sure the nand firmware is a valid firmware with .img in the file name?

m.vgunten · 2018-07-17T04:29:30.484Z

Hi alzhao

I tried different NAND firmwares with .img filename. Currently I am using http://download.gl-inet.com.s3.amazonaws.com/firmware/ar300m/nand/tor/openwrt-ar300m-nand-tor-2.264.img (MD5: 5079e0bae08676b0280f5bbda18c2308.

Running run bootcmd from the U-Boot console correctly boots into the NAND firmware!

Thank you and best regards
Martin

m.vgunten · 2018-07-22T07:24:04.175Z

I resolved marking the device as tested executing the following commands in the u-boot console:

# prepare in memroy
cp.b 0x9fff0000 0x81000000 0xffff
mw 0x81000050 0x646f6e65	# done
mw 0x81000060 0x7365636f	# seco
# write to flash
protect off bank 1
cp.b 0x81000050 0x9fff0050 4 # done
cp.b 0x81000060 0x9fff0060 4 # seco
protect on bank 1

Now I am happy with my cool AR300M booting to NAND and/or NOR using the switch

ylame · 2018-09-12T21:23:32.017Z

@m.vgunten Thank you, I had the same problem and your solution fixed it.

nopro404 · 2018-09-18T14:41:36.408Z

I updated the uboot from here: uboot-for-qca95xx/bin at master · gl-inet/uboot-for-qca95xx · GitHub
It shows its version as U-Boot 1.1.4-g36de7573 (May 26 2017 - 14:42:18)

I had the same problem as @m.vgunten and needed to mark the unit as tested for it to boot up by default. The commands listed worked. Thanks

I also have the problem that boot_dev does not work with the switch with the case on. As noted by @vigans the switch has three positions and without the case on I can put the switch into the right position to boot NOR.

Am I reading correctly that @mkroes erased all the uboot variables and that fixed the switch to work with boot_dev and the case on?

I am reluctant to try this without confirmation. Wouldn’t I have to re-input all the uboot environment settings for uboot to boot the firmware again?

m.vgunten · 2018-09-18T17:24:48.852Z

Hi nopro404
Regarding the three switch position: my simple hack was using a file to have all three switch positions working
And when erasing all the uboot variables the defaults will be set on next boot (you can have a look at the source code GitHub - gl-inet/uboot-for-qca95xx: ar300m uboot source - src/include/configs/board953x.h).
Regards Martin

nopro404 · 2018-09-18T17:53:33.273Z

m.vgunten:

Regarding the three switch position: my simple hack was using a file to have all three switch positions working

Very good, thanks for the clarification.

m.vgunten:

And when erasing all the uboot variables the defaults will be set on next boot

Great to know. Did this help you in some way? Did you just run:

setenv variableName

For each variable and then saveenv to commit?

m.vgunten · 2018-09-18T18:55:19.260Z

For each variable and then saveenv to commit?

No, no setenv/saveenv after erasing, just reboot to u-boot … envvars will then be set to defaults!

nopro404 · 2018-09-18T19:56:00.015Z

Well, I want to add that the new Uboot is way better than the NAND only version shipped with my AR300M. No MTU issues - uploading the firmware is now flawless on Windows. This is the way it should have been on release. If any current AR300M user has this old Uboot, I would highly suggest not testing unknown images on your device without upgrading Uboot to this version.

I did not even solder the board. I paid $1 at the local electronics shop for the UART and 3 female to male breadboard cables and just placed the pins in the provided holes on the board. Worked fine.

juniorjpdj · 2018-10-28T01:50:10.255Z

How can I do this without going to u-boot console?
What does it actually do?
What are this addresses?
Or can I at least enable netconsole in this u-boot?

EDIT: Not needed anymore, I’ve bought USB-TTL converter and did it from u-boot console.

cyablo · 2019-04-04T06:32:01.034Z

Does anyone have a copy of the fixed uboot? The attachement on alzhao*s post seems to be gone and the bin from github still is wrong.

Entropy512 · 2019-04-09T20:28:55.327Z

alzhao:

@vigans, I test again. boot_dev works. The only problem is position is reversed related to the docs. Now if it is left side, it will boot nor.

1. Left side (near the reset button) –> Nand flash 2. Right side –> Nor flash

Just fixed and here is the new uboot.

Here? Where? There is no attachment and no link, and as others have mentioned - the file on github is old. It does not support NAND flashing from TFTP (no “nlf” command defined per documentation in https://docs.gl-inet.com/en/2/hardware/ar300m/ ) and the mode switch is not usable without physical case modifications.

alzhao · 2019-04-11T08:05:10.675Z

The post is old so links was lost.

But I just verified this issue. There is a problem and pls allow some time to find out. So do not need to change uboot at this point.