Hello team,
with 32GB DDR booted the board with the prebuilt image flashed on SD card with switch setting to boot from SD 32GB capacity with single partiton with offset from 131072 for P1
image : lx2160acex7_2000_700_3200_8_5_2_sd_ee5c233.img.xz (downloaded )
The edk2 images are only firmware and are meant to boot generic Aarch64 distro installers. If you are booting from the sdhc card then you can grab any recent Debian, Ubuntu, Fedora installer image and put it on a USB stick, and then boot from there. Note that for full networking support the Installer Image will need a 5.14 kernel or newer. For some tips you can take a look at our DevCuts video here, SolidRun DevCuts - HoneyComb Distro Install - YouTube
If you would like to boot a device-tree based BSP image then you can download that from here, SolidRun Images and flash that to your SDHC card.
Thanks for the info , I flashed the below image and this command. Single partiton with offset from 131072 for P1
xz -dc lx2160acex7_2000_700_3200_8_5_2-bc46e34.img.xz | dd of=/dev/sdX bs=4k conv=fdatasync
when booted i am seeing the below error . My requirement is device-tree based BSP image.
yes so i have flashed only the lx2160acex7_2000_700_3200_8_5_2-bc46e34.img on the SD card and put on the board. and while booting the board is showing above error and stopped.
Execution FW failed (error code -5)
As i understand with the above image Boot default kernel should come up and boot.
if not could let me know the steps. if any live debug possible do let me know.
It would appear that some of the memory calibration fixes I have added to the UEFI edk2 builds are required for your memory configurations. I will need to talk with the BSP team about integrating them. Or if you are willing to build your own boot image I can instruct you on the patch you most likely need.
Thanks…
As we have some 10+ boards to bring UP it will be great if we get the image to verify the board .All basics are working fine. later i will bring up the build setup.
While that code is being used for the edk2 based firmware it is still not validated with the NXP BSP codebase. The team is working on this but images will not be available until all internal testing is done with our validated memory modules. As I said before you are welcome to use our container based build system to include the patch, or do you initial validation with our SystemReady ES firmware and a standard distribution.
Hell team,
Thanks
I could able to boot now but find few issues after booted to EMMC. I could hardly able to edit once “boot” cmd is given.
vi /etc/ssh/sshd_config
/bin/sh: 120: vi: not found
cat /etc/ssj^H
cat: ‘/etc/ssj’$’\b’: No such file or directory
cat /etc/ssh/sshd_config
cat: /etc/ssh/sshd_config: No such file or directory
cd /etc/ssh
/bin/sh: 123: cd: can’t cd to /etc/ssh
ls
bin dev extlinux lib media opt root sbin sys usr
boot etc home lost+found mnt proc run srv tmp var
uname -a
Linux (none) 5.10.35-00001-gb998eddab2c6 #1 SMP PREEMPT Mon Mar 7 12:07:50 IST x
Let me know how to go ahead and get proper login and proceed.
Hello team,
could you help me with the any default install packages scripts or details which vendors usually use… so that at once i can update the required all features.
and as i understand I have to delete the current emmc partition and make it complete 64GB of space.
Once you have the system installed you can refer to the Ubuntu documentation for your specific installation needs, and features such as resizing the filesystem. This page may be useful to you. MetaPackages - Community Help Wiki
Thanks team,
but my generic boot kernel i am seeing this issue once i updated the emmc and boot
is there any way to get proper login point any specific check.
Or if i can push only Uboot - DDR image changes on the genric image on SD card flashed with lx2160acex7_2000_700_3200_8_5_2-a393e2e.img from release mail.
i can boot to normal login