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

Building Source Code does not boot Livebook #198

Open
ks0m1c opened this issue Apr 13, 2022 · 2 comments
Open

Building Source Code does not boot Livebook #198

ks0m1c opened this issue Apr 13, 2022 · 2 comments

Comments

@ks0m1c
Copy link

ks0m1c commented Apr 13, 2022

Building the firmware directly from the source following the steps below results in the RPI 4 to continue blinking but not connecting to the WIFI (seen from network scan)

# Set the MIX_TARGET to the desired platform (rpi0, bbb, rpi3, etc.)
$ export MIX_TARGET=rpi4
$ mix deps.get
$ mix firmware
$ MIX_TARGET=rpi4 NERVES_WIFI_SSID='$WIFI' NERVES_WIFI_PASSPHRASE='$PASS' mix burn
I tried option 2 as well after booting the compiled install as well but it disconnects from the ip address and does not run the process at port 80
# Option 2: Upload to an existing Nerves Livebook device
$ mix firmware.gen.script
$ ./upload.sh [email protected]

The [compiled release] (https://github.com/livebook-dev/nerves_livebook/releases/download/v0.5.7/nerves_livebook_rpi4.fw ) works great but I can't modify the mix.exs to include a phoenix client library I need to directly communicate to websockets

@fhunleth
Copy link
Contributor

That looks like it should work. I'm out of town and don't have a Pi4 to test with. Since I do this regularly, I suspect that it would work for me and there's something else going that's not immediately obvious to me.

One question, does this work without the phoenix client library added to the dependency list? Like could it be related to the dependency or one of its dependencies? This happens every once in a while and usually it's not a hard fix for me if you tell me the library.

@ks0m1c
Copy link
Author

ks0m1c commented Apr 14, 2022

Indeed I had suspected the same and removed from the mix.exs file when it was initially not working

{:phoenix_client, "~> 0.3", , targets: @rpi_targets},

I haddecided to eliminate all variables and try a clean build from source and see where I was going wrong from there when I encountered this issue. I was unsure how to go about debugging and arriving at the core of the issue when I couldn't connect to the RPI over the wifi network and then tried option 2 before I opened the issue here.

I am thinking of trying out the process again with another RPI I have in school after this weekend and see where it leads me.

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