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 to rpi4 project upgrade failure #6

Closed
jsimmonds2 opened this issue Aug 6, 2019 · 4 comments
Closed

rpi3 to rpi4 project upgrade failure #6

jsimmonds2 opened this issue Aug 6, 2019 · 4 comments

Comments

@jsimmonds2
Copy link

Environment

  • Elixir version (elixir -v):

Erlang/OTP 22 [erts-10.4.3] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [hipe]

Elixir 1.9.0 (compiled with Erlang/OTP 22)

  • Nerves environment: (mix nerves.env --info)
    |nerves_bootstrap| Environment Package List

    Pkg: nerves_system_br
    Vsn: 1.8.5
    Type: system_platform
    BuildRunner: {nil, []}

    Pkg: nerves_system_rpi4
    Vsn: 1.8.2
    Type: system
    BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

    Pkg: nerves_toolchain_arm_unknown_linux_gnueabihf
    Vsn: 1.2.0
    Type: toolchain
    BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

    Pkg: nerves_toolchain_ctng
    Vsn: 1.6.0
    Type: toolchain_platform
    BuildRunner: {nil, []}

|nerves_bootstrap| Loadpaths Start

Nerves environment
MIX_TARGET: rpi4
MIX_ENV: dev

|nerves_bootstrap| Environment Variable List
target: rpi4
toolchain: /home/jhs/.nerves/artifacts/nerves_toolchain_arm_unknown_linux_gnueabihf-linux_x86_64-1.2.0
system: /home/jhs/.nerves/artifacts/nerves_system_rpi4-portable-1.8.2
app: /home/jhs/src/RasPi3BPlus/Blinkers/Nerves/fb2

|nerves_bootstrap| Loadpaths End

  • Additional information about your host, target hardware or environment that
    may help

Just taking a simple project that makes working firmware for rpi3 and changing target to rpi4 with this git diff

Screenshot from 2019-08-06 21-53-13

Current behavior

Include errors, stacktraces, screenshots or code that may help us reproduce the
issue.

Screenshot from 2019-08-06 22-15-06

Expected behavior

Nice firmware file that I can try out in my shiny new RPi4 :)

@fhunleth
Copy link
Member

fhunleth commented Aug 6, 2019

Is the project overriding the fwup.conf file? The reason I ask is that fixup.dat isn't used on the RPi4. It got renamed to fixup4.dat. There's a similar change with start.elf going to start4.elf. The config.txt and device tree overlay files also changed.

I think it would be useful to compare the fwup.conf file that you have with https://github.com/nerves-project/nerves_system_rpi4/blob/master/fwup.conf. If I remember right, it should a be a bunch of renames and the device tree file.

@jsimmonds2
Copy link
Author

Many thanks for the help !
Yes, my little project is indeed overriding fwup.conf . . simply to install the spi1-3cs overlay.
Happy now :)

@jsimmonds2
Copy link
Author

( don't know whether comments on Closed Issues reach anyone . . but, for the record, . . )
Thanks to the Nerves core team for providing Raspberry Pi 4 Model B support in Nerves so quickly !

I'm now busy fixing code with silly blind time-delays in initializing an I2C device 😮 because of the extra speed of the RPi4B vs the RPi3B+

@fhunleth
Copy link
Member

fhunleth commented Aug 8, 2019

We get an email, but they're real easy to miss since we're not being reminded by an open issue.

Thanks for letting us know. The RPi4 port took me longer than I was expecting, and it makes me happy that it's working. After ElixirConf US, I hope to start upgrading my Raspberry Pi projects too.

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