MickeyOoh

MickeyOoh

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.

Showing Posts 1 to 2

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 OP

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.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
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
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
Aludel - LLM Evaluation Workbench Aludel is an embeddable Phoenix LiveView dashboard for evaluating and comparing LLM prompts across mult...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews