Hi, everybody.
My boss bought a couple of LigoWawe LigoDLB Propeller 5 thinking that they were already supported by LEDE.
Unfortunately, he was wrong.
So I was given the task of trying to get LEDE running on it.
Stock firmware had a great troubleshooting feature that pretty much exports configuration of everything on the device including GPIO pins and rest.
So LEDs and reset button were easy, got MAC offsets and configured the single port that is connected via MII to AR9342
But I am now stuck, stock firmware does some kind of firmware verification before flashing.
TFTP flashes stock firmware without issues, I also tried to flash sysupgrade image over TFTP but after flashing all I got was LEDs flashing in a row.
It would really ease development if I got access to serial, but the case looks like I would need to destroy it in order to open it and access UART header.
Device specs are following:
AR9342-BL1A
16 MB of flash (Winbond W25Q128FVFG)
64 MB of RAM (Winbond W9751G6KB-25)
1 POE IN 100 Mbit port
So it should run LEDE without a problem, but LigoWawe uses dual firmware.
So when first firmware fails to boot 3 times the second one gets loaded.
So effective space is 8MB.
@ElektromAn Thanks,but it is actually not missing.
Also, I did not understand your statement that startup script is asking for something.
Can you explain that?
Well, I dont understand the issue.
Everything regarding machine name looks to be correctly setup.
In bootlog you can see it: MIPS: machine is LigoWawe DLB-5
Your Board name "DLB-5" is correct for boot the kernel.
After this some other things must happen.
i.e. for OM5P
look in git grep -l om5p target/linux/ar71xx/base-files/
but all this happens in your rootfs.
But you need to fix the VFS issue to see this.
Since it is ar71xx dts is not used,but mach.
I have a feeling that that could be issue with AR8032 configuration.
In stock bootlog it loks like MII is used instead of RGMII