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 :)
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 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 am currently setting up a microcontroller with several libraries which need to be built from source. Using pre-built binaries is not an option due to the system architecture. Building dependencies takes a lot of time and I want to avoid having to do it again for every similar device I need to setup in the future.
Thus, my question is, how can I migrate custom built binaries to another machine of similar architecture?
Any solution that would mirror the whole system to another drive works, too.
Note: For my current use case I am running Ubuntu 18.04 off a MicroSD plugged into a Jetson Nano
Any solution that would mirror the whole system to another drive works, too.
Proposed Solution :
Create a backup of the MicroSD card which has all required binaries installed
Use the backup to mirror the stuff into different MicroSD cards.
Backing Up Your SD card
Connect the SDcard to your laptop
Use dd command to take a backup of your MicroSD card
sudo dd if=/dev/sdxx of=backup.img status=progress
Restoring your backup to a New SD Card
Connect the New SDcard to your laptop
Use dd command to restore the backup to New MicroSD card
sudo dd if=backup.img of=/dev/sdxx status=progress
Note: Your SD card may also show up as /dev/mmcxx or /dev/sdxx depending on how you connect it to your laptop.
Warning: While running dd command, Please make sure that /dev/sdxx is your SD card and not your Hard Disk.
Running this command will tell you the device name of your SD card.
sudo fdisk -l
Please refer to this link for more.
I have an embedded system running Linux, with many peripheral devices connected.
There are some storage devices connected too. Currently, we do not have any diagnostics tool to check the state of devices on the system.
what I want to do with this diagnostics tool is something like:
After connecting to my embedded system either via USB or network port, I want to be able to browse storage media ( in read only mod ), and may be later in future extend this to check the status of other devices running.
With this question, I am seeking guidance of expert people who have faced similar problem and were successfully implement a solution.
I am not looking for a solution but a likely approach.
thanks
one approach is that (it totally depends on your embedded board)
if your board supports booting from the usb, you can modify your bootloader code to boot linux initrd image from the usb, if usb is plugged in your board, otherwise noraml booting procedure.
you can write one c diagnostic utility to check the status of different peripherals and generate the report on the usbdisk
create Linux initrd image for your board with modified rcS file to mount the usb in Linux and start the utility while boot up, copy the utility in bin folder of your rootfilesystem.
now when you power-on your board with usb connected, your testing software will boot and test the peripherals otherwise your normal software will boot.
hope this 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