tamago: Unable to get example working for RPi Zero
Hi folks,
I’ve had an issue open on the RPi Zero example repo for a month, but realised that may not be the right place to post this problem!
Building the example RPi Zero project (with some tweaks, to fix the go.mod file) creates a kernel file which builds successfully, but fails to run on any of my RPi Zeros.
These are the files I’ve had on my SD card, but I get no flashing LED, no printed output and no clues I know how to follow as to further debugging (I also tried including bcm2708-rpi-zero-w.dtb as it’s called out as missing in the UART log, with no luck).
How should I proceed in trying to fix this?
UART Output
Raspberry Pi Bootcode
Read File: config.txt, 279
Read File: start.elf, 2955648 (bytes)
Read File: fixup.dat, 7311 (bytes)
MESS:00:00:01.002000:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:01.006316:0: brfs: File read: 279 bytes
MESS:00:00:01.062589:0: HDMI0:EDID error reading EDID block 0 attempt 0
MESS:00:00:01.068754:0: HDMI0:EDID error reading EDID block 0 attempt 1
MESS:00:00:01.075090:0: HDMI0:EDID error reading EDID block 0 attempt 2
MESS:00:00:01.081427:0: HDMI0:EDID error reading EDID block 0 attempt 3
MESS:00:00:01.087764:0: HDMI0:EDID error reading EDID block 0 attempt 4
MESS:00:00:01.094100:0: HDMI0:EDID error reading EDID block 0 attempt 5
MESS:00:00:01.100437:0: HDMI0:EDID error reading EDID block 0 attempt 6
MESS:00:00:01.106774:0: HDMI0:EDID error reading EDID block 0 attempt 7
MESS:00:00:01.113111:0: HDMI0:EDID error reading EDID block 0 attempt 8
MESS:00:00:01.119448:0: HDMI0:EDID error reading EDID block 0 attempt 9
MESS:00:00:01.125543:0: HDMI0:EDID giving up on reading EDID block 0
MESS:00:00:01.131252:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:01.136292:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
MESS:00:00:01.163018:0: brfs: File read: 279 bytes
MESS:00:00:01.343494:0: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
MESS:00:00:01.349317:0: *** Restart logging
MESS:00:00:01.353713:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 0
MESS:00:00:01.361298:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 1
MESS:00:00:01.368156:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 2
MESS:00:00:01.375014:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 3
MESS:00:00:01.381870:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 4
MESS:00:00:01.388729:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 5
MESS:00:00:01.395586:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 6
MESS:00:00:01.402443:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 7
MESS:00:00:01.409302:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 8
MESS:00:00:01.416158:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 9
MESS:00:00:01.422775:0: hdmi: HDMI0:EDID giving up on reading EDID block 0
MESS:00:00:01.428679:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 0
MESS:00:00:01.436472:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 1
MESS:00:00:01.443329:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 2
MESS:00:00:01.450187:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 3
MESS:00:00:01.457044:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 4
MESS:00:00:01.463902:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 5
MESS:00:00:01.470760:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 6
MESS:00:00:01.477617:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 7
MESS:00:00:01.484475:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 8
MESS:00:00:01.491333:0: hdmi: HDMI0:EDID error reading EDID block 0 attempt 9
MESS:00:00:01.497949:0: hdmi: HDMI0:EDID giving up on reading EDID block 0
MESS:00:00:01.503563:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
MESS:00:00:01.512308:0: HDMI0: hdmi_pixel_encoding: 162000000
MESS:00:00:01.518005:0: vec: vec_middleware_power_on: vec_base: 0x7e806000 rev-id 0x00002708 @ vec: 0x7e806100 @ 0x00000420 enc: 0x7e806060 @ 0x00000220 cgmsae: 0x7e80605c @ 0x00000000
MESS:00:00:01.539405:0: dtb_file 'bcm2708-rpi-zero-w.dtb'
MESS:00:00:01.543299:0: dtb_file 'bcm2708-rpi-0-w.dtb'
MESS:00:00:01.548141:0: Failed to load Device Tree file 'bcm2708-rpi-0-w.dtb'
MESS:00:00:01.555008:0: Failed to open command line file 'cmdline.txt'
MESS:00:00:01.719713:0: brfs: File read: /mfs/sd/example-pi-zero.bin
MESS:00:00:01.724374:0: Loading 'example-pi-zero.bin' to 0x8000 size 0x161050
MESS:00:00:01.731301:0: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
MESS:00:00:01.739720:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:01.746151:0: uart: Baud rate change done...
MESS:00:00:01.749584:0: uart: Baud ratel1pageTableStart 0x4000
l1pageTableSize 0x4000
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (8 by maintainers)
FYI we have identified the likely cause and we are working on a solution, should be done next week.
Thanks, we’ll try to reproduce this and get back to you.
Fixed in https://github.com/f-secure-foundry/tamago/commit/ddf03422d158c43a773ae431044557aeb2eb0040
Can you try with it?
We will try to reproduce as time allows (Pi support is not our primary focus and the PR on kenbell repository certainly is reaching the right person for this). Nonetheless we will try to take a look and get back to you.
In the meantime please make sure that tamago-go and tamago are up to the latest version (the UART output suggests an older version).
Thanks