CaptChrisD
I am working on a custom device tree overlay. I have done these for years on BBB but when trying to do it on a Raspberry Pi I am running into some trouble.
I use Buildroot packages to do this so it is nicely contained.
On the BBB in my Makefile I have:
define MM_FSERIES_DTS_INSTALL_TARGET_CMDS
cp $(@D)/*.dtbo $(TARGET_DIR)/lib/firmware
endef
On the Raspberry pi I have tried to place it in the same path as the other overlays are by default:
define MM_FSERIES_DTS_INSTALL_TARGET_CMDS
cp $(@D)/*.dtbo $(TARGET_DIR)/images/rpi-firmware/overlays/
endef
I tried leaving it in the ./package/ dir:
define SV_GATEWAY_DTS_INSTALL_TARGET_CMDS
cp $(@D)/*.dtbo $(NERVES_DEFCONFIG_DIR)/package/sv-gateway-dts/
endef
Either way I cannot get fwup to find the file with an error like: fwup: can’t open path ‘$(NERVES_SYSTEM)/images/rpi-firmware/overlays/sv-gateway-01.dtbo’ in file-resource ‘sv-gateway-01.dtbo’
Anyone created custom overlays for Pi systems willing to let me in on the correct incantation?
Trending in Questions
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 5 of 5 Posts
CaptChrisD
It appears the issue may be that the package is not compiling…
I am doing everything the same as when adding a custom package to a BBB system. Since there are no custom Buildroot packages already in a Pi system is there an extra step?
I created:
packagedirectoryadded
source “$NERVES_DEFCONFIG_DIR/package/extra-leds-dts/Config.in”toConfig.inI even added
packagetopackage_files/0in themix.exsfile to make sure it was used in the hashI am using the same package layout as I am on the BBB just changing the
dtsfile to be Pi specificI am seeing the package appear in the menuconfig and selecting it is adding it to
nerves_defconfigbut when conducting the compile I don’t see it in the list with all the legal info gathering like I do in the BBB system.fhunleth
Without seeing the code, it’s hard to say for sure, but my bet is that there’s a typo in the
extra-leds-dts.mkfile since I do that frequently. Maybe runmake extra-leds-dts-rebuildto see or look for the build directory.Having said that, I have a couple things:
$(BINARIES_DIR), but I’d copy to a different directory from therpi-firmwarepackage’s output directory. I’d probably just put it in the root images directory if it’s only one file.config.txtas well. That seems to be the path you’re going down.dtoverlayprogram. I’d also compile your overlay as part of your Elixir project and put the.dtboin aprivdirectory so there’s nothing you need to do with Buildroot or Nerves Systems at all.Hope that helps.
CaptChrisD
Update:
I am able to compile now but still can’t get the dtbo file to land somewhere I can use it.
To enable compiling I had to add
external.mkto the nerves system like the bbb system has.So the outstanding issue is getting
define MM_FSERIES_DTS_INSTALL_TARGET_CMDScp $(@D)/*.dtbo $(TARGET_DIR)/images/rpi-firmware/overlays/endefThe TARGET_DIR is not appropriate but cannot figure out what variable to use
lawik
did you try BINARIES_DIR that Frank mentioned? That’s the images dir typically in my experience
CaptChrisD
Finally got this working. Thanks @fhunleth for the assistance on finding the correct variable.
To make this work you have to:
external.mkfile to the root of your pi systempackagedir at the root of your pi systempackagetopackage_files/0in themix.exsfile. When changes in the version occur it will be rebuilt.nerves_defconfigfwup.confto include the new dtbo (see below)config.txtto load the new overlayHere is a complete Makefile for a custom device tree overlay
Then in your
fwup.conffile you can access this file withThen in your
config.txtadd:dtoverlay=custom