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 had built a Yocto image from honister branch. I created a bootable USB drive and flashed my image into it. Whenever I wanted to boot into the USB drive, I am always given 3 different choice:
boot, install, Reboot Into Firmware Interface
This is a picture of what I see when I boot:
My question are there any way I can make my yocto image in my USB drive to boot straight into the OS without giving any of those options?
Do I need to make the needed configuration in my already built image or I need to rebuild the image after changing some configuration in my poky or any other meta layers?
Thanks,
Hari
I just started working with a Beagle Bone Blue and I have installed the necessary drivers however when I go to http://192.168.7.2/, it say the site cannot be reached because it took too long to respond. I would really appreciate it if someone would help be. Thanks!
I think the kernel image you are using in BeagleBone Blue must be properly booted in the board or if you are using eMMC0 for booting the board,
Check the kernel logs of booting using minicom in Linux or putty/Terraterm in Windows.
Also, check if there is one folder creating as BeagleBone(Getting Started) in Windows after proper booting done.
If you are using Linux, check the same type of folder and verify the internet connectivity.
Try to use new kernel image available from https://beagleboard.org/latest-images
Boot it using sd Card and flash it on the board.
Then, try 192.168.7.2 in the browser.
It will be working if you follow the proper steps.
I hope it helps.
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
I downloaded the hard float image of Raspbian here:
http://www.raspberrypi.org/downloads
I copied the recommended hard-float image on an SD card and the Raspberry Pi boots fine with it.
Then I downloaded the soft-float version of Raspbian because I need it to get some software running that does not work on the hard-float version. I formatted the SD card again, copied the soft-float image onto it and tried to boot the Raspberry Pi with it.
Problem: the Raspbery Pi doesn't boot with the soft-float version of Raspbian!! I see the green "ACT" LED light up for less than a second. After that only the red power LED is on and nothing happens after that.
I repeated this process a couple of times and redownloaded the images, checked the SHA of the downloaded file, etc. It just doesn't work. The hard-float image always boots up (green "ACT" light flashes rapidly like normal).
Any ideas?
Update: If you have a newer Raspberry Pi with Hynix memory then the older versions of Raspbian will not boot. Specifically you'll need at least the 2013-02-09 Debian 7 (Wheezy) build.
See this post.
Now, the 2013-02-09 Wheezy build is a hard-float version, so you can't use that, but you can update the kernel image of your soft-float version which is actually independent of the Linux OS (I'm told that basically the GPU boots the Raspberry Pi, and it runs the ARM as a kind of co-processor). So, you can run rpi-update to update your kernel, and it should be all OK.
There's a bit of a catch-22 if you don't own any of the older Raspberry Pis that will boot the older images--how can you update the OS if the only Raspberry Pi you have is a newer one which won't boot? In your case it sounds like you have access to an older one, so you're OK. For those who don't, maybe someone will eventually post an updated soft-float version, but until then perhaps you can try the following. I haven't; it's just a theory, but at this point you don't have much to lose :-)
Burn the latest Wheezy image (2012-02-09) to an extra SD card
Mount this SD card on Windows
Copy all the files except *gz ones which correspond to the Linux filesystem. Basically, all the boot images and configuration files
Mount the SD card containing your soft-float image and overwrite the boot image files
Hopefully have a beer to celebrate?
Previous post:
Yes, I had this same problem. I don't know exactly what is wrong, but the start_elf image won't boot, at least with the recent set of Raspberry Pis. I can't believe Raspbian would release something that broken, so I suspect it works for some Raspberry Pis, but not others. What you need to do is:
Burn the hard-float copy of Wheezy to an SD card. You're going to snatch off the boot image (which works) and copy it to the soft float one.
Mount the SD card on a Windows machine. The boot partition is FAT, so you'll be able to see it. Look for the file start.elf. Copy it to your Windows machine.
Burn the soft-float copy of Wheezy to an SD card and mount it on the Windows box.
Replace it's start.elf with the copy from your hard-float one.
Crack open a beer and enjoy.
See my related post.
Just image one card with hard-float(Raspbian “wheezy”), and the other
with soft-float(Soft-float Debian “wheezy”). Plug both into a Windows PC and
copy all files (you can see at all) from the hard-float onto the
soft-float card, replacing existing ones.
Explanation: http://www.raspberrypi.org/archives/3534
P.S. You can, of course, copy those files to a temporary folder first,
swap cards and then replace all files on the soft-float card with
those in the temporary folder.
bootcode.bin
start.elf
fixup.dat
From Raspberry Pi SD card with this Soft-float Debian "wheezy" did not want to boot
When you dd the image, make sure bs=1M...
After trying all the things in the other answers, it was finally the way to make it work on a latest Raspberry Pi out of the box. I've actually found this a good help with several Raspberry Pi applications/code.