I accidently modified uEnv.txt file located in eMMC of my Beaglebone black. Now the board is not booting. I can not even see BBB for serial connection from terra term. How can I get access to the board? If I can just access to uboot I could reflash or run it using nfs. Any ideas?
You can boot via normal microSD card as described here:
burn a bootable image on your microSD card
insert this card
power up your BBB while holding USER/BOOT button
once in Linux - repair your uEnv.txt on eMMC
Related
I have built an image for the TQ Systems STKa8x Evaluation board with an i.MX8 QuadMax using the yocto project. The resulting image does not boot on the device. Can anyone help me interpret the warnings and errors occuring in the serial console output when trying to boot?
I think the the machine configuration might be wrong? The device hardware is ok, becaus the device boots using the included sd card.
Did you flash your Yocto image in your emmc or SDcard ? Here it seams that there is no partition table in your emmc which is normally embedded inside Linux image. It is more likely that the flash did not succeed.
Plus you can see warning from u-boot that he cannot load the device tree. Check your repository build/tmp/deploy/image/machine/*.dtb
You should also check if your linux image and device tree is flashed in the correct address.
Solved: The problem was caused by the SD card. I have used this SD card https://de.transcend-info.com/embedded/product/embedded-memory-cards/usd230i. Using another one solved my problem.
I followed this tutorial to boot the ULTRA 96 :
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841783/Building+Xen+Hypervisor+with+Petalinux+2018.1
I'm using petalinux-v2018.2-final and xilinx-ultra96-reva-v2018.2-final.bsp
I built the project myself then copied necessary files into the SD card (BOOT.bin,xen.ub.system.dtb,image,rootfs.cpio.gz.u-boot) int the boot partition and the rootfs files(extracted from rootfs.cpio) into the root partition of the SD card. I even tried copying the same files from the pre-built images in the project but there is no response at all from the card when I enter sudo screen ... or even when I tried with trace32.
please help I'm stuck here and thank you for your time!
Update:
when I copied the prebuilt images and connected the board to a screen via display port, the system boots and opens a Linux kernel based system but when i searched if it's a Dom 0 for the xen i didn"t find anything( when I entered dmesg | grep xen it showed nothing). My problem is if this system is the Dom 0 for xen or it's simply a linux image on my board and thank you :)
I begin embedded Linux with BeagleBone Black. I use crosstool-NG to build U-boot. Result is file MLO and u-boot.img, which was wrtite into SD cards.
Then, I insert SD cards into BeagleBone Black to test.
I follow this decription https://elinux.org/Building_for_BeagleBone#U-Boot
But, it don't show #U-boot.
Note that i just test uboot, not kernel image and root file system. And a uboot image is available on the onboard eMMC.
How do I fix it?
Thank you!
I have my raspberry pi zero, and during development I spend a lot of time to eject-inject SD card and re-flash it. SD card image is prepared in Buildroot, so it includes boot partition with kernel, device tree overlays and partition with rootfs.
Is there simpler way to re-flash SD card? For example via network? I know that U-boot can load kernel via tftp, but if I need not only kernel, but whole image(device tree overlays are extremely important)?
Use TFTP to load the kernel image, and NFS to mount the root filesystem over the network.
Am stuck in making a bootable SD-Card.
I have gpt_both0.bin, hyp.mbn, NON-HLOS.bin, rpm.mbn, sbl1.mbn, sec.dat, tz.mbn, emmc_appsboot.mbn, boot.img and rootfs.img files.
When i flash all of 'em into eMMC (using fastboot command) the board boots easily and we dont face any problems. But now i also have to make a bootable SD-Card to boot board via SD-card.
Can anyone please explain how can i achieve this !
I am using Ubuntu-14.04 on my PC.