nrf 9160 modem programming issue

RE: nrf 9160 modem programming issue

Michal — Tue, 03 Sep 2024 17:02:05 GMT

[quote user="Hjalmar"]Ok, the alternative method works when I program in 64 k sections ONLY.[/quote]

I will ask for the details about that.

Also, does that mean that this has managed to help you solve the issue completely?

RE: nrf 9160 modem programming issue

Hjalmar — Mon, 02 Sep 2024 12:07:46 GMT

Ok, the alternative method works when I program in 64 k sections ONLY.
The recommended doesn't work on our chips that we just bought from digikey and has 1.1.6 (that requires the correct fw that for the later modems )

RE: nrf 9160 modem programming issue

Michal — Tue, 27 Aug 2024 12:05:20 GMT

Sorry for the delay, here are some notes from our engineers:

4.4.1 Recommended method

This method is supported for modem firmware versions from 1.3.5 and higher.

2. Split the contents of the HEX file into contiguous sections that are 8 KB aligned and up to 56KB large.

3. Write the data to 0x2000001C + offset, where the offset is 0 or 0xE000.

Add a new step between 3. and 4.:
If not programming the first section, poll IPC.MODEM_CTRL_EVENT…

4: If all sections not yet programmed, write the following

4a: starting → target

5: last page → last section

7. Poll IPC.MODEM_CTRL_EVENT. If you get 0x5A000001, the command is not supported, and you should use the alternative method instead. You should get 0xA5000005 if the command succeeded.

9: pages → sections

9: Step 4 → (New step between 3. and 4.)

consider copying IPC.MODEM_CTRL_EVENT response description from 'Alternative method' step 5.

4.4.2 Alternative method

2. Split the contents of the HEX file into contiguous sections that are 8 KB aligned and up to 64KB large.

4.5 Verifying the modem

The digest is in 0x20000010-0x2000002C, stored in little-endian words. For example, a digest of 925372E7512EBE1C06805F6BC58721BBE2ED2A82F362F05151ED25FBB2A48E4D would read out as the following words: {0x925372e7, 0x512ebe1c, 0x6805f6b, 0xc58721bb, 0xe2ed2a82, 0xf362f051, 0x51ed25fb, 0xb2a48e4d}.

Ranges in the digest.txt file are given in inclusive notation, so “0x00006000--0x0000FFFF” would be a length of 0xa000 (40KB).

RE: nrf 9160 modem programming issue

Hjalmar — Mon, 26 Aug 2024 15:26:50 GMT

ping?

RE: nrf 9160 modem programming issue

Michal — Thu, 22 Aug 2024 19:38:53 GMT

I have found out a few things internally, I'll try to summarize it to you tomorrow.

Best regards,

Michal

RE: nrf 9160 modem programming issue

Michal — Tue, 20 Aug 2024 18:45:49 GMT

Just wanted to let you know, that we are still looking into it. It is quite a complicated question, so I'm not exactly sure when I will have more information, but I will get back to you when I will find out more.

Best regards,

Michal

RE: nrf 9160 modem programming issue

Michal — Fri, 16 Aug 2024 12:12:45 GMT

Hello,

Thank you for the update.

We are looking into it internally and I will hopefully have some more information next week.

Please let us know if you get any further in the meantime.

Best regards,

Michal

RE: nrf 9160 modem programming issue

Hjalmar — Fri, 16 Aug 2024 08:23:07 GMT

**UPDATE**

After sniffing how nrfjprog does this, verification now works, the trick is that you can't send larger chunks than 65k for verificationm, I have also verified this with the python code, where your python code gets the same error as I had before changing to only verify 65 k chunks at the time..

Also, note that you can't verify the first file, ie on adress 0x59602000 with length 2360, since then it responds with an error.

I still don't get the programming to work, so please, can you send me the relevant sections of nrfjprog python code so I can get that to work?