Timing out waiting for ack or nack response

[Elp03]

Hi!
I am using a probe-rs for programming nrf9151, and I have a problem with the program not functioning due to timing out waiting for ACK or NACK.

I have tried to set the speed down, and then I got further in programming the Nordic chip, but it still times out waiting for ACK or NACK.

Here is the error message with a speed of 1.

cargo run --bin updater -- program path/mfw_nrf91x1_2.0.2.zip 
   Compiling modem_updater v0.1.0 (path/modem_updater)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.62s
     Running `target/debug/updater program path/mfw_nrf91x1_2.0.2.zip`
[2025-04-29T08:12:39Z INFO  modem_updater] UICR.HFXOSR is not set, setting it to 0x0E
[2025-04-29T08:12:39Z INFO  modem_updater] UICR.HFXOCNT is not set, setting it to 0x20
[2025-04-29T08:12:49Z INFO  modem_updater] ACK response, code A5000001
[2025-04-29T08:12:49Z INFO  modem_updater] modem_firmware_loader version: 2.1.0
[2025-04-29T08:12:49Z INFO  modem_updater] Using pipelined loader
[2025-04-29T08:12:49Z INFO  modem_updater] Inserting segment: 0:firmware.update.image.segments.0.hex
[2025-04-29T08:12:49Z INFO  modem_updater] Inserting segment: 1:firmware.update.image.segments.1.hex
[2025-04-29T08:12:49Z INFO  modem_updater] Parsing segment digests
[2025-04-29T08:12:50Z INFO  modem_updater] Firmware digest: 056C7DA80536A2AEA9EBEC3855A3D977F41B814237E5922809D4E7306BB14D92
[2025-04-29T08:12:50Z INFO  modem_updater] Programming modem firmware loader: /tmp/.tmpt6Dri4/21746FD.ipc_dfu.signed_2.1.0.ihex

thread 'main' panicked at src/bin/updater.rs:122:43:
called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "Timeout waiting for ACK or NACK response" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

``

[jaredwolff]

I've had the same issue. Will push a fix today.

[jaredwolff]

@Elp03 pushed. Give it a go

[Elp03]

Hi!
Thank you for a quick reply. Unfortunately, it still doesn't work for me.
I get the following output:

cargo run --bin updater -- program path/mfw_nrf91x1_2.0.2.zip 
   Compiling modem_updater v0.1.0 (path/modem_updater)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.62s
     Running `target/debug/updater verify path/mfw_nrf91x1_2.0.2.zip`
[2025-04-29T16:39:24Z INFO  modem_updater] UICR.HFXOSR is not set, setting it to 0x0E
[2025-04-29T16:39:24Z INFO  modem_updater] UICR.HFXOCNT is not set, setting it to 0x20

thread 'main' panicked at src/bin/updater.rs:122:43:
called `Result::unwrap()` on an `Err` value: Timeout
stack backtrace:
   0: rust_begin_unwind
             at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/std/src/panicking.rs:692:5
   1: core::panicking::panic_fmt
             at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/core/src/panicking.rs:75:14
   2: core::result::unwrap_failed
             at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/core/src/result.rs:1704:5
   3: core::result::Result<T,E>::unwrap
             at /home/athamantis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:1109:23
   4: updater::main
             at ./src/bin/updater.rs:122:9
   5: core::ops::function::FnOnce::call_once
             at /home/athamantis/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I would like to add that I am using a rusty probe on a custom PCB, and thus have changed the VID and PID parameters. I can upload firmware with this setup.
Again, thank you for your support.