Very useful guide by #WhitneyKnitter on @hackster_io
A few updates though:
--get-hw-description simply use the directory into which Vivado spat your .xsa file upon hardware export.Oh, and a general hint: upon installing #petalinux, the docs state, that --dir sets the installation directory. Yeah, but only if said directory exists. Otherwise it’s silently ignored and installation goes to current working directory. Because, duh, I guess -.-
As the occasional #petalinux -user (which sits on top of yocto if I see this correctly) I’m happy to hear about the funding!
It's amazing how much of Computer Science is actually about learning yet another package management system.
For me (in that order): #FreeBSD ports, libtool user-land madness, #Debian packages, and now #Petalinux recipes.
Never getting boring...
Last week we looked at how we could use spidev and I2Cdev to work with devices which use SPI or I2C interfaces. These are commonly used interfaces for a range of devices (e.g., ADCs, DACs, and sensors). Of course, one of the things we want to do with PetaLinux is work with the custom logic functions in the PL. There are two ways we could create a driver for our custom PL module. We can do this be either creating a kernel module and running from kernel space or creating a driver in the user space
Any #uboot (the #bootloader) experts here? I’m trying to boot a #PetaLinux image, but I get
Verifying Hash Integrity ... sha256 error!
Bad hash value for 'hash-1' hash node in 'ramdisk-1' image node
Bad Data Hash
Ramdisk image is corrupt or invalid
Booting using Fit image failed
even though when I extract the image (no matter whether with dd or dumpimage), the resulting SHA256 _does_ match the checksum listed in the #FIT. What’s going on?