pelwell
commented
2 years ago What are you trying to achieve with dt-blob.bin? You are probably better off without it.
Closed nbuchwitz closed 2 years ago
pelwell
commented
2 years ago What are you trying to achieve with dt-blob.bin? You are probably better off without it.
popcornmix
commented
2 years ago dtblob.dts "updated" to a stale version when we bumped to 5.15 from the next branch. I've updated master branch version to latest (which includes cm4s support).
pelwell
commented
2 years ago Thanks. My question still remains though, @nbuchwitz - why do you need an external dt-blob.bin?
nbuchwitz
commented
2 years ago @pelwell Nothing specific. Just stumbled over the entry in vcdbg logs, while I was debugging another issue. The dt-blob.bin exists in our image mostly for historical reasons and probably can be removed safely.
@popcornmix I tried with your updated version and the message is gone (also when the file is absent and the included one is used)
If there aren't any objections, I will close this issue. Thanks a lot!
pelwell
commented
2 years ago We rarely object to issues being closed.
l1k
commented
2 years ago What are you trying to achieve with dt-blob.bin? You are probably better off without it.
Our use cases for dt-blob.bin comprise:
We've noticed that most of what is configured in dt-blob.bin can also be configured in the HAT EEPROM, albeit only for bank 0. That's a problem for us. Is there any chance that you could extend the HAT EEPROM spec and firmware support to allow for setting up the upper banks as well on boot?
nbuchwitz
commented
2 years ago Thanks for the clarification, @l1k
l1k
commented
2 years ago @popcornmix: The dt-blob.dts contains two entries for the CM4S which look fishy:
pin_define@EMMC_ENABLE {
type = "internal";
number = <49>;
};
pin_define@LEDS_DISK_ACTIVITY {
type = "internal";
number = <46>;
};On the CM1, EMMC_ENABLE is number 47 and on the CM3, it's number 1.
On both, LEDS_DISK_ACTIVITY is absent.
Please confirm that these two CM4S settings are correct.
Moreover, the pin_config section is missing the entries for EMMC_ENABLE_N polarity, SD drive strength, SMPS_SCL/SDA and Hotplug. I'm wondering if that's on purpose or an oversight?
pelwell
commented
2 years ago GPIO49 is a signal called EMMC_DISABLE_N (i.e. EMMC_ENABLE), which is tied high. GPIO46 is inconnected, so the LEDS_DISK_ACTIVITY is vestigial (but does avoid a warning).
Describe the bug
After booting a CM4s there is an entry in vcdbg log which complains about a potential bad
dt-blob.bin:I tried to compile a more recent version from https://github.com/raspberrypi/firmware/blob/master/extra/dt-blob.dts (
stableandmaster), but the message still appears in the log.To reproduce Boot a CM4s device and run
vcdbg log msgExpected behaviour
dt-blob.binis loaded and no message is presentActual behaviour See bug description above
System Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
cat /etc/rpi-issue)?vcgencmd version)?uname -a)?Logs vcdbg log msg
Additional context Add any other relevant context for the problem.