Closed jphastings closed 3 years ago
abarisani
commented
3 years ago 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
jphastings
commented
3 years ago Thank you @abarisani; I recognise the RPi isn't a core part of your work and really appreciate the time you've taken! I'm interested in contrinuting and helping to fix this (both for myself, and for others) — if you've even any 'gut' instincts they'd go a long way to helping me, as my professional experience is on the web stack, not kernel!
I'll keep exploring, and trying to reach @kenbell for advice, but in the meanwhile (for reference), I'll post any advances in this thread.
Just to ensure this wasn't a versioning issue, I made sure I was using commit 9f55bc1 — the most recent that works with the current 1.16.3 latest.zip pre-build tamago-go. I also added dtdebug=1 in config.txt, but I can't see anything else useful in there.
I've been exploring the RPi's UART configuration, as the final lines appear slightly garbled, and they're just after a log line declaring a resetting of the UART baudrate; but with no luck.
Tips, from anyone, much appreciated!
abarisani
commented
3 years ago Can you please try with tamago HEAD and our latest tamago-go binary release? Thank you.
jphastings
commented
3 years ago Hey @abarisani, thank you for the update; sadly I'm not getting past the build step:
$ docker run -v $(pwd):/workdir jphastings/tamago-build:v1.16.4
/root/go/pkg/mod/github.com/f-secure-foundry/tamago@v0.0.0-20210512135525-47ab2cac2668/soc/bcm2835/bcm2835.go:58:5: ARM.CacheEnable undefined (type *arm.CPU has no field or method CacheEnable)You can see I'm using the latest commit of tamago (47ab2cac2668), run with the tamago 1.16.4 binary build. I've not delved into why this error might be occurring yet, not have I (yet) tried using the source-built tamago-go.
I'll take a look into this, but it's likely beyond my knowlegde!
abarisani
commented
3 years ago Fixed in https://github.com/f-secure-foundry/tamago/commit/ddf03422d158c43a773ae431044557aeb2eb0040
Can you try with it?
jphastings
commented
3 years ago It successfully builds, but never appears to execute the application code in a way similar (but not identical) to above.
Now I'm getting no output after the Baud rate change I'm worried I'm missing further debug info because it's switching rates.
I've been monitoring the output with a separate serial USB device, and screen /dev/cu.usbserial-0001 115200, and the config.txt set to:
enable_uart=1
uart_2ndstage=1
dtparam=uart0=on
kernel_address=0x8000
disable_commandline_tags=1
core_freq=250
kernel=tamago-kernel.binI realise tis is Pi-specific stuff, but if you know the lack of further output is expected, or some part of this config isn't helping you debug, just mention it!
abarisani
commented
3 years ago Thanks, we'll try to reproduce this and get back to you.
jphastings
commented
3 years ago I've refreshed my memory of RPi UART usage and tried a number of scenarios, without any change or luck. This includes:
core_freq and enable_uart assertions in config.txt (as they seem mostly related to miniUART, and on the RPi Zero, the PL011 is default/primary anyway)dtoverlay=disable-bt line in cmdline.txt (along with that overlay from the rpi repo, at overlays/disable-bt-overlay.dts) — as this ensures that the PL011 is primary (this looks to be already the case, from the logs above, but worth a try!)Thank you for your help!
abarisani
commented
3 years ago FYI we have identified the likely cause and we are working on a solution, should be done next week.
jphastings
commented
3 years ago Thank you! I'm looking forward to it 😊
andrejro
commented
3 years ago The issue has been solved now. Please try our fork: https://github.com/f-secure-foundry/tamago-example-pizero
jphastings
commented
3 years ago Thanks @andrejro! Your fork seems to be using an old version of tamago (maybe you didn't push your changes to your fork?) so I did the following, but still have no luck:
$ git clone git@github.com:f-secure-foundry/tamago-example-pizero.git
# Get rid of old go mod file
$ rm go.*
# Use latest tamago
$ go mod init
$ go mod tidy
# Ensure we're using the latest tamago
$ cat go.mod
module github.com/f-secure-foundry/tamago-example-pizero
go 1.16
require github.com/f-secure-foundry/tamago v0.0.0-20210601073428-3d51445fa773
# Build with tamago-go
$ docker run -v $(pwd):/workdir -v /Volumes/SDCARD:/workdir/build jphastings/tamago-build:HEAD
Downloading RPi firmware: LICENCE.broadcom
Downloading RPi firmware: bootcode.bin
Downloading RPi firmware: fixup.dat
Downloading RPi firmware: start.elf
go: downloading github.com/f-secure-foundry/tamago v0.0.0-20210601073428-3d51445fa773
Volume SDCARD on disk3s1 unmounted(This was built with tamago-go built from source @1.16.4, in this docker container using this definition)
Am I missing something?
andrejro
commented
3 years ago I forgot to push on the repo, sorry. Please retry now.
jphastings
commented
3 years ago It works beautifully! Thank you for the hard work @andrejro 😊
I have some time (and interest) in continuing to develop tamago-build, to allow mac users (like myself), windows users, or linux users without a cross compile set up to build apps with tamago — if that's something you think your team would be interested in, I'd love a chat to make sure I'd be building in the same direction you are.
Thanks again!
abarisani
commented
3 years ago It works beautifully! Thank you for the hard work @andrejro
I have some time (and interest) in continuing to develop tamago-build, to allow mac users (like myself), windows users, or linux users without a cross compile set up to build apps with tamago — if that's something you think your team would be interested in, I'd love a chat to make sure I'd be building in the same direction you are.
Thanks again!
Sure thing, sounds definitely interesting.
jphastings
commented
3 years ago PR added here to cover that (just to join up the threads — I'll await your thoughts & feedback over there)
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.dtbas 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 ```