Hi bodhi, the number on the chip says macronix MX25L1606E which corresponds with the current kernel dmesg. However you are correct that the stock kernel detects it differently. Koen stock: [ 27.165642] m25p80 spi0.0: mx25l1605d (2048 Kbytes) current: [ 1.830166] m25p80 spi0.0: found mx25l1606e, expected sst25vf080bby Koen - Debian
Hi bodhi, when I run the ping test this is the output: T5325> ping 192.168.1.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.1.1 is not alive T5325> and the dhcp boot test results in this: T5325> dhcp BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 BOOTP broadcast 6 BOOTP brby Koen - Debian
Hi bodhi, still can't save envs from Debian. Koen root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x000000 0x010000 0x1000 root@debian:~# root@debian:~# fw_setenv koen test root@debian:~# root@debian:~# fw_printenv | grep koen root@debian:~#by Koen - Debian
Ok here are the outputs. root@debian:~# dmesg | grep -i10 'mtd partition' [ 1.774725] console enabled [ 1.781845] bootconsole disabled [ 1.791580] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 22, base_baud = 10416666) is a 16550A [ 1.802556] sata_mv f10a0000.sata-host: version 1.28 [ 1.802719] sata_mv f10a0000.sata-host: slots 32 ports 1 [ 1.820391] scby Koen - Debian
After setting up the environment variables I can boot back into Debian. However after messing up I can't go back to stock anymore since I don't have backups of all the original mtd partitions. So if someone is willing to share their "permanent u-boot env", "HP env" and "SSD firmware" mtd partitions that would be great. Koenby Koen - Debian
OK I've managed to read the spi chip with flashrom following the instructions on this website: https://www.rototron.info/recover-bricked-bios-using-flashrom-on-a-raspberry-pi/ (I didn't desolder the chip but used a 8 pin clip instead) I then needed to create a file to write back to spi. I'm not sure if flashrom can write only certain sections of the spi chip so I decided tby Koen - Debian
Switching off ipv6 didn't make a difference. So I decided to try to go back to stock which was a mistake. mtd layout in Debian: root@HP5325:/koen# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00010000 "uboot" mtd1: 00040000 00010000 "sdd_firmware" mtd2: 00010000 00010000 "uboot_env" mtd3: 00010000 00010000 "permanent_uboot_env&qby Koen - Debian
Hi bodhi, I've adjusted the fw_env.config file but can not modify envs from Debian. It does not really matter since I've got serial connection but I would like to understand why it is not possible. I've tried flash_unlock but this doesn't make a difference. Is it locked down in uboot by the manufacturer? Or do need to do a chmod on /dev/mtd1? Koenby Koen - Debian
I can list envs in Debian using the fw_env.config below. However I can only set envs using serial. Is there a way to be able to set envs from Debian? Koen root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x000000 0x010000by Koen - Debian
I've replaced the battery with a spare one of an old laptop motherboard. I've set the time, used a fixed ip and played around with different ethtool options but nothing seems to make a difference, I still can't get a connection. So the only thing left to test would be to go back to stock to see if it is a hardware problem. Koenby Koen - Debian
Hi, I run alt-f firmware on my DNS325. It may be worth looking through the source code or asking on their forum. Koen https://sites.google.com/site/altfirmware/homeby Koen - Debian
No I've not tried ethtool yet. I'm not familiar with it so I'm not sure what to change / test. So I need to search for some troubleshooting tutorial online first. Koenby Koen - Debian
Ok I've checked the date and time are correct in uboot and set the following ip address in uboot: 192.168.1.225. Next I boot into Debian and setup a static ip address as follows: root@HP5325:~# cat /etc/network/interfaces auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.1.225 netmask 255.255.255.0 gateway 192.168.1.1 where 192.1by Koen - Debian
I've adjusted the date and time and plugged in the cable a few times but it doesn't make a difference. After rebooting the date and time are still correct but the connection still doesn't work unfortunately. Should the date be set in uboot instead? Edit: Just checked uboot and the date there now matches that in Debian. So I guess Debian adjusts the hardware clock when the date aby Koen - Debian
I'm running openwrt on my router and there are some messages in the kernel log and system log: [51046.970755] lantiq,xrx200-net 1e108000.eth eth0: port 1 lost link [51053.114620] lantiq,xrx200-net 1e108000.eth eth0: port 1 got link [52101.664636] lantiq,xrx200-net 1e108000.eth eth0: port 1 lost link [52105.759848] lantiq,xrx200-net 1e108000.eth eth0: port 1 got link [54811.099124] lby Koen - Debian
Below the steps I've done to re-flash uboot and the uboot environment variables from Debian. root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00080000 00010000 "u-boot" mtd1: 00040000 00010000 "SSD firmware" mtd2: 00010000 00010000 "u-boot env" mtd3: 00010000 00010000 "permanent u-boot env" mtd4: 00010000 00010000 "perby Koen - Debian
Cool. ChipPC doesn't give much info about the device but I hope the info in this thread will help you to get started. Koenby Koen - Debian
OK I will have a look at going back to stock to see if it is a hardware issue. Without working ethernet the device is of not much use so may as well give this a try. Accessing the mtd partitions from Debian doesn't work properly on my box at the moment so I guess the best way is via serial connection. I've not got much time this weekend but will start reading up on this so I've gotby Koen - Debian
Hi bodhi, I'm getting the same result as fortis91 when doing the 2 tests. I've tried kwboot multiple times but have never got the box to respond. Not sure why since I know the serial connection works fine. I still have backups of the stock mtd0 and mtd3 partitions. Is it worth going back to stock and test the networking to see if it might be a hardware problem? Koenby Koen - Debian
Chip number is 88E3016-NNC1 Koenby Koen - Debian
From Debian I've copied the 5 mtd partitions to the USB stick using the following command: dd if=/dev/mtd0 of=t5325.mtd0 bs=64k conv=sync dd if=/dev/mtd1 of=t5325.mtd1 bs=64k conv=sync dd if=/dev/mtd2 of=t5325.mtd2 bs=64k conv=sync dd if=/dev/mtd3 of=t5325.mtd3 bs=64k conv=sync dd if=/dev/mtd4 of=t5325.mtd4 bs=64k conv=sync I've powered down the device and put the USB stick iby Koen - Debian
Hi bodhi, your dmesg looks very similar to mine The main differences are highlighted below. It is a different board revision and uses a different flash chip. bodhi: mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3 jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. m25p80 spi0.0: m25p80 (1024 Kbytes) koen: mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2 jffs2: version 2.2.by Koen - Debian
Hi fortis91, I have the same problem and have not found a solution yet but will have another look at the issue. Can you share the setting of /etc/fw_config that is used to be able to adjust uboot variables from Debian? One thing that does stand out in your dmesg log is the following line: [ 0.022045] : /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is noby Koen - Debian
Hi bodhi, I've tried the approach with the additional 'run bootcmd_bootm' in the middle and the SD card removed. Unfortunately the device does not continue with step 4 but instead goes into stock recovery mode and tries to boot from the network. So I guess I'll stick to my script on the SD card approach which works as intended. Koen Hit any key to stop autoboot: 0by Koen - Debian
Hi bodhi, the SD card can easily be replaced if it would ever get damaged so I am using that as the default option. The internal memory can't be replaced so that would be used as rescue / recovery system. So the two boot options are: boot from SD card if present otherwise fall back to booting the rescue system from internal memory. As far as I can see that is only possible by moving the &by Koen - Debian
Hi bodhi, I guess overwritten was not the best choice of words. If I understand your proposed solution correctly the command 'run set_bootargs_sd' always gets executed before booting. This happens after 'run set_bootargs_int' so the bootargs always end up being set to the following value: console=ttyS0,115200 root=LABEL=rootfsSD rootdelay=10 ${mtdparts} earlyprintk=serial.by Koen - Debian
Hi bodhi, I've been thinking about that approach but I'm not sure it would work. If the SD card is removed and the device rebooted the bootargs will get overwritten to 'root=LABEL=rootfsSD' while it should remain 'root=LABEL=rootfsINT'. Koenby Koen - Debian
Either I'm making a mistake somewhere or this version of uboot doesn't seem to like parameter substitution in scripts. Using the following complete line in the script does work: setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfsSD rootdelay=10 mtdparts=spi0.0:768k(uboot),256k(uboot_env),768k(uboot2),-(kernel) earlyprintk=serial' as shown by dmesg: [ 0.0000by Koen - Debian
The script does work but is not completely correct since dmesg shows the following: 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfsSD rootdelay=10 ${mtdparts} earlyprintk=serial resulting in this: root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00200000 00001000 "spi0.0" root@debian:~# It seems that ${mtdparts} does not get replacby Koen - Debian
The following method works to make the device boot from SD card when present or otherwise from the internal memory: Create a file changeLabelSD.txt which contains the following line. This script adjusts the root file system label which is passed to the kernel to avoid confusion. setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfsSD rootdelay=10 ${mtdparts} earlyprintk=serial'by Koen - Debian