LigoWave LigoDLB Propeller 5

@robimarko Fetch 902-at803x-add-reset-gpio-pdata.patch to target/linux/ar71xx/patches-4.4/ and rebuild kernel.

That patch is already in LEDE

@robimarko, REPLACE patch and rebuild.

Ok, rebuilding now
Update: It works, thanks.
Boots fine and network works also.

Now I gotta figure out how to make device specific patch because boot counter needs to be reset,otherwise device boots to second firmware after 3 reboots.

I don't get what is the difference in patch.

Pointer checking :slight_smile:

Then It is weird that that patch is not in LEDE.
So that is basically now preventing me from adding this device to official LEDE.

MAC is read correctly, gotta fix LEDs since they dont work.
Weirdly they are not set to 1 and manually I can turn them on so that means that GPIO is correct.

Invert .active_low to active_low = 0 and add .default_state = LEDS_GPIO_DEFSTATE_ON if you want to enable it when kernel initialized gpio.

Patch for patch sent to @nbd :slight_smile:

Thanks, but they are actually active when low.
The issue is that LED configuration was not generated.
When manually configured they work without an issue.

Also sysupgrade does not work because board_name is set to unknown.
Most likely I did not configure platform.sh correctly

Thanks for patch

Where it live? in u-boot environment or in ART partition?

U-boot environment.
The issue is not how to reset the counter, but instead how to do it in a way that device can still be officially supported by LEDE.
In stock firmware they this in rc.sysinit

#reset recovery mode counter in u-boot environment
[ -x /usr/sbin/fw_setenv ] && /usr/sbin/fw_unsetenv linux_fail linux_fail1 linux_fail2
[ -x /usr/sbin/factoryd ] && /usr/sbin/factoryd -t
/usr/sbin/sysconf -e

fw_setenv from uboot-envtools, so try set every boot linux_fail1=0 linux_fail2=0.

Thanks, gotta figure out how to do that automatically with official LEDE.
It looks like issues with LED configuration are caused by board_name being set to unknown.
I gotta check that

Sysupgrade and LED issues resolved.
Those were caused because board_name was not set.

Got bootcounter reset working also.
After your patch for AR8032 is merged I will open a PR.

Still gotta test updating from stock WEB UI

No, although WEB UI accepts and does the update it does not work.
They use their custom fwupdate utility and it looks like flashing through it won't work.
So I think I won't bother even trying and will just post TFTP instructions.
The same image works without an issue if flashed over TFTP.
Here is boot log: