Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Mon, 12 May 2025 12:19:07 GMT

When the JEDEC ID is read as 0, it means the chip did not respond (MISO kept low during the transfer). However, it’s interesting that you were able to communicate with the chip after swapping to the wrong node. Please ensure that the correct CS pin is connected.

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

mark_82 — Mon, 12 May 2025 11:27:50 GMT

Yes. The above output is when I swap two nodes. However, the original code I run was:

and it was the same result as run your 1212.hex on my board. Do you mean I have to insure CS P0.10 is configured as an OUTPUT if I enabled AT45DB1 node (original code no changed)? Why my JEDEC ID read out is 00 00 00? What is your terminal result when you generating 1212.hex?

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Mon, 12 May 2025 07:07:50 GMT

The log output shows that the driver is now able to read the JEDEC ID from the chip. It also indicates that you have disabled the AT45DB1 node and instead enabled AT45DB0, which uses P0.20 for CS.

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

mark_82 — Fri, 09 May 2025 11:48:00 GMT

Hi,

I found that my CS P0.10 -> PIN_CNF[10] is set as an INPUT. How can I set it as OUTPUT without changing the original code? Why is your default setting as OUTPUT? Any other pins I need to set to OUTPUT bare in mind?

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Thu, 08 May 2025 13:47:38 GMT

I'm just trying to understand what I'm missing, as it doesn't make any sense that CS on P0.10 isn't being toggled when we're testing with the exact same firmware.

[quote user="mark_82"]How can I check and change this pin configuration register to set as an output? [/quote]

Start a debug session using our VS code extension and use the Peripherals View to view the GPIO configuration.

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

mark_82 — Wed, 07 May 2025 16:32:53 GMT

Why does it matter? My CS P0.10 signal is always staying HIGH when I flash your hex. How can I check and change this pin configuration register to set as an output?

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Wed, 30 Apr 2025 13:07:28 GMT

Are you checking the CS signal on P0.10? You can also check the pin configuration register to confirm it's set as an output, and verify that the signal toggles when you manually set the output low in OUTSET.

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

mark_82 — Wed, 30 Apr 2025 09:40:54 GMT

Hi,

The firmware you sent is not working as well!

The command line run:

PS D:\Documents\GunfireTracker\Apps\spi_flash_at45> nrfjprog --program 1212.merged.hex --chiperase --reset
[ #################### ]   0.587s | Erase file - Done erasing
[ #################### ]   0.514s | Program file - Done programming
WARNING: A programming operation has been performed without --verify.
WARNING: Programming can fail without error.
Applying system reset.
Run.

The UART VCOM running your *.hex the same as my build:

[00:00:00.252,960] <27>[1;31m<err> spi_flash_at45: Wrong JEDEC ID: 00 00 00, expected: 1F 27 01<27>[0m<\r><\n>
*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***<\r><\n>*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***<\r><\n>
DataFlash sample on nrf9160dk<\r><\n>at45db321e@1: device not ready.<\r><\n>

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Tue, 29 Apr 2025 17:04:58 GMT

You should get an error if there were any issues with loading of the hex file. Did you check the debug log output or probe the bus lines after you programmed this hex?

You can also program the hex with nrfutil from the command line:

$ nrfutil device program --firmware merged.hex --options chip_erase_mode=ERASE_ALL,reset=RESET_PIN,verify=VERIFY_READ

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

mark_82 — Tue, 29 Apr 2025 15:58:53 GMT

Hi, I am using nRF Programmer to flash my board. I press "flash & write" button and it never shown green blocks? Any other way I can flash the hex?

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Tue, 29 Apr 2025 09:52:58 GMT

Hello,

I did not make any changes to the sample. CS was on P0.10 and MOSI on P0.12. Attached is the merged.hex from my build. Could you try it and see if you get the same result?

devzone.nordicsemi.com/.../1212.merged.hex

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

mark_82 — Mon, 28 Apr 2025 11:37:04 GMT

Hello,

Now, I enable at45db0 node to status = "okay"; and disable at45db0 node to status = "disabled". The prob result are both of P0.10 and P0.20 are always staying HIGH and P0.11 (SCK) NO constant clocking output! It is the same result as I swap the node. Which pin did you probe on your waveform? P0.15 -> CS and P0.13 -> MOSI? Did you assign it to different pins when you running the original sample?

RE: Issue of Nordic AT45 DataFlash driver demo on (nrf9160dk/nrf9160) board.

Vidar Berg — Sat, 26 Apr 2025 06:05:05 GMT

Hello,

I don't have this device to test with, but I was able to get the CS to toggle by running the original sample project on my nRF9160 DK:

Did you probe p0.10? P0.20 is the CS assigned to the disabled at45db0 node.

Best regards,

Vidar