spi_nor device id 00 00 00 does not match config c2 28 17

[SerJo]

I'm trying to make work an nrf9160dk which use bme280 (and possibly other sensors) and mx25r64 (integrated in the nrf). I use than the golioth platform to make dfu through lte-m.

Using ncs 2.2.0 I've to made some changes in glolioth sdk and zephyr too due to malformed include. But now the build goes fine.

The issue is that when I flash I get this error:

Ignore the mqtt. I use mcuboot.

I attached the relevant files. In the overlay there's a custom mx25r64 configuration but it doesn't work, so I'm currently using the one provided by nrf dtsi.

[Naeem Maroof]

Hi,

Thank you for contacting DevZone at NordicSemi.

I can see that you have attached image snapshots of your configurations and overlays.

I would like to get your minimal project in zip file (including proj.conf, overlays, and main.c etc).

This way I should be able to reproduce the error you are facing and start digging into it.

Please click on "Insert"-->"Image/video/file" and then on the "upload" button under the File/URL bar (as shown here)

This will allow you to browse and select the file. Please attach only a single (zip) file including all project.

Regards,

Naeem

[SerJo]

Hi, probably there's some damage. I tried with another board and it works. How can I see if there's a damage? Through voltmeter is possible or it's useless?

[Naeem Maroof]

Hello,

Good to know that it is working for you.

Can you check what things you are doing differently this time?

Sometime loose or bad connections can cause a lot of problems.

Can you make sure your connections are good. And as I said, what changes you have made (if any)?

If it is the DK, then you can probably flash basic examples and see if it is working good or not. Using a voltmeter you can check expected value on the pins.

[SerJo]

Sorry I already said it. Simply I change board.

[SerJo]

Well, now it boot up but says this:

I have to make a pm_patitions.yml file? I remember a time ago I see some config_ about primary and secondary partitions involved in this, but I don't find it anymore. I'm working with 2.2.0 if you don't remember.

[SerJo]

I don't know why there's two golioth initialization and then suddenly stops. I think it's connected to boot process, but one time at a moment.

[Naeem Maroof]

From the time stamps, they both seem to be the one and same log.