I have a target in the form of the Buffalo LS421DE two disk NAS. I have a compiled image to put onto to the board from a series of three patches submitted July 2015 by Daniel Golle. See the links for reference:
I have soldered up a USB TTL serial adapter and have console. U-Boot is readily accessible from the terminal and I can also get the board to transfer the compiled image over TFTP. However I am trying to figure out how to get U-Boot to successfully boot the image and properly modify the setenv. Any ideas?
Given the boot logs it has been done before and I am trying to put together a complete guide on how to do it.
This is wonderful news and thanks for submitting the patches. I should log into the OpenWRT forums more often. It's been over two years but it is good to see this little device supported. Now to find a couple of 4TB drives and put it back together.
Here's to hoping the cat has not killed the power supply cord... (Om nom nom chew.)
Any modification about setenv to do after openwrt install ?
I have no TTL console and made a full from linux installation of my LS421DE...
all is OK except that I need to remove the disk at power up for boot in nand OpenWRT
The Uboot env is read only in this device. Therefore you can't use a hard drive with the stock OS installed because it will allways boot from this media. The best option is to keep apart this hard drive (useful if you want back to stock firmware), and insert a new formatted one. Or you can also format the stock hard drive if you have no intentions to back to stock firmware.
It might also be possible to use a modded U-boot to skip the stock command line and boot from NAND even if a hard drive with the stock firmware is present. But this isn't straightforward.
I never had this problem. Is it a hard drive without partitions?
Well I don't remember if I made tests with different filesystem formats. I almost always used a hard drive with a XFS partition in my tests. Probably I also used ext4.
Resolved, by formatting the partition with xfs, the NAS boot up now correctly.
I suppose that the ext4 partition is discovered by uboot and break bootup of OpenWrt from NAND !
Thanks for reporting. I'll add the tip to the wiki.
XFS is used for data and ext4 for the stock OS, maybe it hangs while looking for the stock OS files. BTW I'll make more tests to see if we can solve this problem adding a dummy partition or another trick.
I'm testing crypto improvements with the Marvel CESA engine. I installed the cryptodev driver with openssl.
However I'm having some troubles with the digest algorithms, they return a wrong checksum from any file. I'm not sure if my hardware has some issue, might be related with the L2 cache.
@erdoukki could you test if it works ok in your Linkstation?. These are the steps:
Install the openssl util opkg update opkg install openssl-util
Create a file big enough in tmp (or on an external hard drive), and make the checksum: cd /tmp dd if=/dev/urandom of=test.bin bs=1M count=128 openssl sha1 test.bin
Install the cryptodev driver and its libopenssl library: opkg install kmod-cryptodev opkg install libopenssl-devcrypto
Enable the crypto device: edit /etc/ssl/openssl.cnf and uncoment devcrytpo under the [engines] section: [engines] devcrypto=devcrypto
Under the [devcrypto] section add the DIGESTS = ALL line: [devcrypto] DIGESTS = ALL
Save the file and make again the test: openssl sha1 test.bin
Could you please share the kernel patch for fixing this issue please? I would like to make my own build as I would like to use the CESA feature. Many thanks!