Hi there!
I've been testing the debian install like documented here in the forums on my NSA325. I've got a serial connection and was successful in running
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
with an attached USB stick prepared with the Debian kirkwood rootfs. So I could test the whole thing, without modifying the original setup.
What I noticed: without an USB stick the new U-Boot does not boot the original stock firmware, but does a reset. I have quite some experience with Linux on Intel systems, but this the first time dealing with the ARM and embedded world. The hardware configuration of these systems seems not being done via hardware scanning, but by using a "device tree" and U-Boot seems responsible initializing the hardware and then starting the linux kernel.
My first question: if I update to a new U-Boot, how can I start the stock firmware? And maybe switch between booting from the internal flash and from USB / disk.
Second question: I've seen several "fw_setenv" commands in the guides here, which set env variables for U-Boot, but I'd like to get more knowledge what's going on. Probably some values are being passed to the Linux kernel, but some also must control the behavior of U-Boot. Maybe someone can point me in the right direction.
Thanks in advance.
I've been testing the debian install like documented here in the forums on my NSA325. I've got a serial connection and was successful in running
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
with an attached USB stick prepared with the Debian kirkwood rootfs. So I could test the whole thing, without modifying the original setup.
What I noticed: without an USB stick the new U-Boot does not boot the original stock firmware, but does a reset. I have quite some experience with Linux on Intel systems, but this the first time dealing with the ARM and embedded world. The hardware configuration of these systems seems not being done via hardware scanning, but by using a "device tree" and U-Boot seems responsible initializing the hardware and then starting the linux kernel.
My first question: if I update to a new U-Boot, how can I start the stock firmware? And maybe switch between booting from the internal flash and from USB / disk.
Second question: I've seen several "fw_setenv" commands in the guides here, which set env variables for U-Boot, but I'd like to get more knowledge what's going on. Probably some values are being passed to the Linux kernel, but some also must control the behavior of U-Boot. Maybe someone can point me in the right direction.
Thanks in advance.