Hi Daniel! Hope you're well and good. >From a first glance, I reckon the issue you are facing is probably due to the >following reasons either in isolation or combination: 1. The vendor's build configuration & your custom build configuration are in conflict with the required infrastructure ( probably vendor dictated infrastructure). 2. The boot is probably vendor-locked. 3. Might be a versioning or build order conflict or linker script issue. Can you check the memory location of the 1st boot sector or "boot-block" for the vendor build? Compare it with your build and see if you can troubleshoot with that approach. And check the first reset location in hex code in case your device powers up but the boot fails.
P.S. Since you're using a yocto build I would suggest trying out with openBMC first then reverse engineer your way into a correct u-boot configuration for your requirements. Thanks & Regards, Rahul
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64712): https://lists.yoctoproject.org/g/yocto/message/64712 Mute This Topic: https://lists.yoctoproject.org/mt/111009769/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
