Hello Mike, I don’t know what your preference regarding setup is, but for me it was crucial to be able to make changes to the rootfs and kernel quickly and to be able to remotely reset the device.
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). 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. With this approach you could for example locate when DPU support that you need was added. Your case seems to be better in one regard though: as you know what you are looking for you can also look at commit messages and the code. In my case I didn’t know what was source of problems - the board just didn’t boot or (in another case) loading ‘nixge’ driver for 10Gb/s ports crashed the board. Piotr
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
