Issues with SPI on iMX7 Sabre Board
Hi all, I'm trying to communicate with SPI in barebox on the MC iMX7 Sabre Board. I added the options in my barebox config: CONFIG_SPI=y CONFIG_CMD_SPI=y But there is no SPI bus when I try to communicate with: barebox@Freescale i.MX7 SabreSD Board:/ spi 0x1 spi bus 0 not found spi: No such device Could someone please tell me if a SPI driver exists for the iMX7 Sabre Board? Thanks a lot, Kai ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Barebox support for Arm Cortex-M0 Boards
Hi everyone, does barebox support any kind of Arm-Cortex M0 Boards? e.g. STM32F0 or similiar? I couldn't find any mention of such a board in the board support section of the documentation. I hope I didn't overlook something. Thanks and best Regards, Kai Che ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
issues communicating with SPI on Raspberry Pi 3
Hi all, I'm trying to communicate with a TPM 2.0 (infineon,slb9670) over SPI on a Raspberry Pi 3 in barebox. CONFIG_SPI=y CONFIG_DRIVER_SPI_GPIO=y CONFIG_CMD_SPI=y are set in the barebox configuration and dtparam=spi=on is set in the /boot/config.txt on the raspberry pi. But when checking /dev/ on barebox, there is nothing related to spi except cs0. I would have expected something similiar to /dev/spidev0.0 showing up. Did I miss any configurations? Best Regrds, Kai Che ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
issues verifying FIT image signature
Hi all,
I'm trying to verify the signature of a FIT image in barebox.
I created the FIT image with the following .its file:
...
configurations {
default = "config@1";
config@1 {
description = "Boot Raspian kernel";
kernel = "kernel";
fdt = "fdt-1";
signature@1 {
algo = "sha256,rsa2048";
key-name-hint = "dev";
sign-images = "fdt", "kernel";
...
Verifying the Hashes for the kernel and fdt-1 works fine ("hash OK" for both
images) , but when I try to verify the signature I get the follwoing error:
ERROR: FIT: hashed-strings start not found in
/configurations/config@1/signature@1
I could follow the error back to the fit_verify_signature function in
/common/image-fit.c file, but I don't understand what is causing the error.
Is the function looking for a string called "hashed-strings" in the FIT image
file? I checked the .fit file (with hexdump) and I could only find the string
"hash@1" which barebox uses to verify the signature.
Best regards
Kai
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
issues loading a FIT image with bootm
Hi all, I'm trying to load a FIT image (image.itb) with the bootm command, but I'm getting the following issue: barebox@RaspberryPi 3 Model B:/ bootm Loading open firmware Device Tree flattened Binary '/mnt/disk0.3/image.itb' no image handler found for image type open firmware Device Tree flattened Binary handler failed with: No such device The generated .itb file is created with mkimage -f from u-boot and according to the patches, the FIT image format should be supported: http://lists.infradead.org/pipermail/barebox/2015-March/022876.html Does anyone have experience with loading and verifying FIT images with bootm and could give me some suggestions on what would I need to check further in order to identify and fix the issue? Thanks, Kai ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Secure boot support
Hi all, I found some patches in 2017 for supporting secure boot on the barebox: http://lists.infradead.org/pipermail/barebox/2017-March/029444.html The git repository provided in the message is a dead link and I can't find more information on it. What happened with it? Can I find the repository somewhere? Best Regards, Kai Che ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Issues compiling barebox on raspberry pi
Hello, I'm trying to compile barebox on the raspberry pi 3 model B and after booting the pi with the barebox-raspberry-pi-3.img I get the following error: barebox 2018.04.0-g9b6b12471 #2 Thu Oct 18 14:33:09 CEST 2018 Board: RaspberryPi 3 Model B bcm2835_mci 3f30.sdhci: registered as 3f30.sdhci bcm2835-gpio 3f20.gpio: probed gpiochip-1 with base 0 malloc space: 0x0fefe700 -> 0x1fdfcdff (size 255 MiB) mci0: detected SD card version 2.0 mci0: registered disk0 environment load /boot/barebox.env: No such file or directory Maybe you have to create the partition. running /env/bin/init... Hit any key to stop autoboot:0 booting 'net' ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed ip_route_get: No such file or directory ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed ifup: No such file or directory running automount command 'ifup -a && mount -t tftp $global.net.server /mnt/tftp' failed open: No such file or directory could not open /mnt/tftp/none-linux-rpi: No such file or directory ERROR: Booting 'net' failed: No such file or directory booting 'net' failed: No such file or directory boot: No such file or directory barebox@RaspberryPi 3 Model B:/ The pi doesn't accept any keyboard input and is "stuck" at this stage. How and where can I get the barebox.env file? Thanks very much and best regards, Kai Che ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
