Be advised that bad configurations of kernel and/or FPGA (or device tree info) can lead to boot loops which are pretty annoying to auto-fix.
--M On Thu, Oct 3, 2024 at 6:21 PM mruane--- via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi Piotr, > > This was especially important when dealing with kernel and bootloader. As > I didn’t have much experience with editing kernel and u-boot sources, it > was indispensable to be able to check my changes and applied patches > quickly (the additional difficulty was that I didn’t have a X410 to see in > action how things should work). > > I have ZERO experience modifying the bootloader. I’ve used TFTPBoot > before, for bootloader, kernel, and rootfs, and it worked well. I’ve never > mounted a remote rootfs over NFS, or loaded the bootloader over JTAG. I saw > some places in the code where you made some NFS- and JTAG-related changes. > I was thinking I would not use that stuff because I have a board on my > desk, but…mounting the eMMC over USB, unzipping the ext4.tar.gz, and > overwriting the correct partition on the eMMC is a REAL pain. And it’s only > a matter of time before I brick the device because I was rushing through > the steps. > > My setup consisted of NFS server hosting rootfs and TFTP server for > kernel. The bootloader was loaded through JTAG. This way I for example was > able to make a script that: compiled and installed new kernel with the > board turned off or in not working state, tried to boot it, check if system > started correctly and return the result to git bisect. This way (after some > fine-tuning) I was able to run ‘git bisect’ and wait for it to find a > commit where the board started to work. If you are interested how to > configure what I’ve described - ask. > > Ok…THAT is a great idea. I’ve been avoiding ‘git bisect’ all this time. > Hahaha I’ll feel guilty for asking how you set that up, but I think I will > be too curious not to. > > You know, with a little scripting, it might be possible to remotely > monitor something on the board that gives an indication of whether it > successfully booted, like RESET BOARD, WAIT FOR N SECONDS, PING BOARD…, and > then automatically tell ‘git bisect’ to keep going or not. If you were only > looking for a successful boot, and you weren’t worried about what the exact > failures were, you could just launch it and work on something else. Hahaha > Sometimes being lazy can be a lot of work for me. > > Mike > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
