flashing u-boot to flash is risky, if it goes wrong then your nas becomes a brick and you need special tools to get it running again.
You also posted in your pm's this screen shot
2big2-ded.JPG
seems that this boot loader loads an kernel with name uImage in the folder with name /boot from partition 1 on the disk in slot 0 that is formatted in ext2 or ext3, or it loads a kernel from USB from partition 1 formatted in FAT again in folder with name /boot
It seems to pass some boot arguments
You could do three things. Prepare a disk with the kernel in partiton 1 in the folder /boot or use usb stick
You could also try if we can change the environmental variables to use the right boot parameters. We need to check if these changes are not overwritten again at boot.
So you could try if the the command setenv works
For instance change the the boot arguments (in u-boot console)
edited 2 apr 14 because of mistake in the code, this is the correct one to be used- Code: Select all
setenv bootargs console=ttyS0,115200 root=/dev/sda7
saveenv
You can check if the change is made by using the command: printenv
Now reboot with the standalone kernel and do again a "printenv" to see if the change is still there
If this is the case then we can adjust the bootcmd and arguments correctly for our firmware.
You do not have the required permissions to view the files attached to this post.