Project

General

Profile

Forums » Software Development »

BNSD image not booting Kernel after shifting design from MitySOM-5CSX-H6-42A to MitySOM-5CSX-H6-4YA

Added by Bob Nayar 3 days ago

I had successfully built images for the MitySOM-5CSX-H6-42A with the Mike's help on this forum.

However, after shifting my design to the MitySOM-5CSX-H6-4YA (and of course, re-doing the project from the Critical Link GIT repo 'dev_5csx_h6_4ya' folder), I am getting the messages shown in the attached image.

Do you know what I could be doing wrong?
Thanks.

Bob N

H6-4YA_not_booting.jpg (107 KB) H6-4YA_not_booting.jpg

Replies (3)

BN RE: SD image not booting Kernel after shifting design from MitySOM-5CSX-H6-42A to MitySOM-5CSX-H6-4YA - Added by Bob Nayar about 2 hours ago

I noticed that in the uBootMMCEnv.txt on the project that generated a proper SD card image, the 'mmcfdtloc' was

mmcfdtloc=/boot/socfpga_mitysom5csx_devkit.dtb

while on the project that did not work, it was set to

mmcfdtloc=/boot/socfpga_mitysom5csx-h6-4ya_devkit.dtb

MF RE: SD image not booting Kernel after shifting design from MitySOM-5CSX-H6-42A to MitySOM-5CSX-H6-4YA - Added by Mike Fiorenza about 1 hour ago

Bob,

The errors in your screenshot are the same line ending issue I described here: https://support.criticallink.com/redmine/boards/47/topics/7453?r=7483#message-7483

Your new dev_5csx_h6_4ya folder is a fresh checkout, so its uBootMMCEnv.txt.orig has Windows line endings again. Run this in that folder, then rebuild the image:

dos2unix software/preloader/uBootMMCEnv.txt.orig
make sd_image

The mmcfdtloc difference you found is expected. The Makefile points each module at its own device tree, and socfpga_mitysom5csx-h6-4ya_devkit.dtb is the right one for the 4YA, so leave that as is.

- Mike

BN RE: SD image not booting Kernel after shifting design from MitySOM-5CSX-H6-42A to MitySOM-5CSX-H6-4YA - Added by Bob Nayar 23 minutes ago

Thanks, Mike.
The DOS2UNIX (which I should have remembered) fixed it.

Bob N

    (1-3/3)
    Go to top