petalinux-boot –jtag –u-boot –hw_server-url TCP:ubuntu:3121
Using the command as above will report an error similar to the one below.
Solution:
Set the compatibility of the virtual machine’s USB device to USB3.1, because the physical USB port my computer is connected to is USB3.1.
INFO: Sourcing build tools
INFO: Launching XSDB for file download and boot.
INFO: This may take a few minutes, depending on the size of your image.
rlwrap: warning: your KaTeX parse error: Expected ‘EOF’, got ‘#’ at position 170: … “name =~ “arm*#̲0″”. available …params(filter)”. available targets:$target_list””
(procedure “targets” line 177)
invoked from within
“targets -set -nocase -filter {name =~ “arm*#0”}”
(file “/tmp/tmp.tUZ8sEM2Wm” line 3)
INFO: The XSDB log is as follows
Read More:
- Petalinux Failed to open PetaLinux lib: librdi_commonxillic.so: cannot open shared object file:
- petalinux-build Error: ERROR: Task (/opt/pkg/petalinux/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/fsbl/fsbl_git.bb:do_compile) failed with exit code ‘1’
- Linux Mint: linuxbrew Install and Boot Error [How to Solve]
- Problem solving / etc/ rc.local The boot entry of the file configuration is invalid
- [Solved] Virtual Machine Boot-up Error: failed to recover intents
- [Solved] ubuntu Boot Error: /dev/nume0n1p2:clean
- Linux Virtual Machine Boot Container: Error response from daemon: driver failed programming external connectivity on endpoint
- U-boot NFS download file error: loading: * * * error: File lookup fail solution
- [Solved] rk3588_buildroot Compile Error: ERROR: Running build_kernel failed!
- /usr/bin/ssh-copy-id: ERROR: No identities found [How to Solve]
- Android: How to Start App Automatically
- [Solved] Log Error: kernel: blk_update_request: I/O error, dev fd0, sector 0
- Ubuntu Run Error: not syncing : VFS: Unable to mount root
- [Solved] Linux virtual machine startup error: operating system not found
- [Solved] Centos Mount Error: XFS: log mount mount/recovery failed : error -117
- CentOS/RHEL 7: How to Reinstall GRUB2 from Rescue Mode (EFI)
- [Solved] NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver
- Centos6.8vnc error: connect: Connection refused 10061
- [Solved] an error occurred when attempting to lock the volume