Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rpi3 and Rpi4 not booting after meta-updater layer integration to Yocto #75

Open
oferorgal opened this issue May 8, 2023 · 4 comments

Comments

@oferorgal
Copy link

Hello all,

After adding meta-updater and meta-updater-raspberrypi layers to yocto build, both Rpi3 and Rpi4 stopped botting from u-boot:

U-Boot 2020.01 (Jan 01 1970 - 00:00:00 +0000)

DRAM:  948 MiB
RPI 3 Model B (0xa22082)
MMC:   mmc@7e202000: 0, sdhci@7e300000: 1
Loading Environment from FAT... OK
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
530 bytes read in 3 ms (171.9 KiB/s)
ostree_root=/ostree/boot.1/poky/23c93b57b6fb5acd8496a969fe7271892a754cad3c3bbf5e062ac7d95feaeff3/0
95 bytes read in 11 ms (7.8 KiB/s)
7539672 bytes read in 317 ms (22.7 MiB/s)
## Loading kernel from FIT Image at 02700000 ...
Could not find configuration node
ERROR: can't get kernel image!
Unknown command '!' - try 'help'
resetting ...

(UART output)

I made the changes to my yocto build manually but after this didn't work I followed the https://docs.ota.here.com/getstarted/dev/raspberry-pi.html tutorial without the "here" credentials (Also replaced advancedtelematics repo with uptane).

Note: All Yocto, meta-* branches are on dunfell.

Did support for the boards stopped at any point? Can you guide me/add to README how to make it work?
Any help would be great.
Thanks,
Ofer.

@oferorgal
Copy link
Author

I was able to fix the problem by changing: bootcmd_run=bootm "${ramdisk_addr_r}${fit_conf}" to bootcmd_run=bootm ${ramdisk_addr_r} ${fit_conf}

Now, I have a different problem on RPi4 that I keep getting this error while the kernel boots:

[    0.512145] brcm-pcie fd500000.pcie: dmabounce: could not allocate 33554432 byte DMA pool
[    0.512162] brcm-pcie fd500000.pcie: could not init bounce buffers: -12
[    0.512198] brcm-pcie: probe of fd500000.pcie failed with error -12
[    0.512496] bcm2708_fb soc:fb: Unable to determine number of FB's. Assuming 1
[    0.512513] bcm2708_fb soc:fb: FB found 1 display(s)
[    0.513021] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001
[    0.513039] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22)
[    0.513081] bcm2708_fb soc:fb: probe failed, err -22
[    0.513105] bcm2708_fb: probe of soc:fb failed with error -22

Any ideas?

@pattivacek
Copy link
Collaborator

Are you using https://github.com/advancedtelematic/meta-updater-raspberrypi? I totally forgot we once had that repo. It was never migrated to the uptane namespace, which was probably an oversight. We wanted to combine it with dynamic layers anyway, but never got around to it.

@oferorgal
Copy link
Author

Yes. I'm using this guide: https://docs.ota.here.com/getstarted/dev/raspberry-pi.html.

@oferorgal
Copy link
Author

It seems that meta-raspberrypi (dunfell) and meta-updater-raspberrypi (dunfell) are not in sync.
For example, meta-raspberrypi kernel version is 5.4 and meta-updater-raspberrypi is 4.19....

Can someone point more changes between them?

Changing meta-updater-raspberrypi to 5.4 fixes the error above but I have new error:

[    3.030159] mmc0: ADMA error: 0x02000000
[    3.034307] mmc0: error -5 whilst initialising SD card

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants