MickeyOoh

MickeyOoh

Nerves: I can't upload firmware for `subsystem request failed` error

After upgrading nerves_bootstrap 1.9.0, I can’t upload firmware to target any more for the error.

  1. mix nerves.new app → make a new project
  2. mix deps.get → The comments came out.
A new version of Nerves bootstrap is available(1.8.1 < 1.9.0), You can update by running

  mix local.nerves
  1. after update the above, mix deps.get runs.
** (RuntimeError) :nerves_ssh isn't configured, but :nerves_firmware_ssh is.

This is probably not right. If you recently upgraded to :nerves_ssh or
a library that uses it like :nerves_pack, you'll need to edit your config.exs
and rename references to :nerves_firmware_ssh to :nerves_ssh.
  1. modified nerves_firmware.ssh to nerves_ssh as the comments in config/target.exe

  2. mix firmware and ./upload_sh execute

 $ ./upload.sh 
Path: ./_build/rpi3_dev/nerves/images/connect.fw
Product: connect 0.1.0
UUID: f524800a-2aa7-5f60-7bec-f3a86f32caa3
Platform: rpi3

Uploading to nerves.local...
subsystem request failed on channel 0

After all I can’t upload because of subsystem request failed

I check the previous project if I can upload or not with compiling processes. This case is all right.
.ssh/id_rsa.pub is the same.
And ssh nerves.local passes to make a remote terminal.
I upgrade fwup 1.8.0 -> 1.8.1 but this didn’t solve the issue.

I assume that ssh_subsystem_fwup which is deps of nerves_ssh has something wrong and I should set something on configuration.

Could you please tell me how to solve this?

Thanks.

First 2 of 2 Posts! Switch mode

fhunleth

fhunleth

Co-author of Nerves

Thanks for posting so many details. I’ll try to explain what’s happening and what you can do to fix it.

The switch from nerves_firmware_ssh to nerves_ssh changes the TCP port number that firmware updates get sent. nerves_firmware_ssh uses TCP port 8989. nerves_ssh uses TCP port 22. Why the change of ports? The short story is that it centralizes SSH daemon configuration - IEx prompt, SFTP, and firmware updates all get authenticated the same way.

It looks like you are using the upload.sh script from nerves_ssh to update a device that is running nerves_firmware_ssh. The "subsystem request failed" error is due to the upload script trying to send the firmware file to an ssh subsystem on TCP port 22. That doesn’t exist with nerves_firmware_ssh so you get an error.

To fix this:

  1. Find a nerves_firmware_ssh upload.sh script or download this one. Call it upload-old.sh
  2. Run ./upload-old.sh to push the new firmware to the device
  3. Subsequent uploads should be done with the new upload.sh script (since nerves_ssh is now running on the device).

Another option is to continue to use nerves_firmware_ssh. If you’re using nerves_pack to pull in firmware update support, lock your nerves_pack dependency to ~> 0.3.0.

I hope this fixes your issue.

MickeyOoh

MickeyOoh

Thanks a lot for your leading.

The trouble of upload has been solved by following your comments.

And I am so sorry to miss reading document although I intended to read it. I should have checked it more carefully.

I appreciate your kind response and help again.

Where Next?

Trending in Questions Top

jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
saveman71
Hello ! We want new/edit form pages to POST/PUT to their own URL rather than the resources REST defaults (post /things, put /things/:id)...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement