Jump to content
  • 0

Can not program the QSPI FLASH on the ARTY Z7-20


Kerem Oktem

Question

Hello,

I have a Digilent ARTY Z7-20 Board. I could program the S25FL128SAGMFI001 QSPI FLASH on the board.

But unfortunately one day while I was programming the flash, a friend of mine accidentally pressed the RESET button the board.

After that, I could not program the FLASH anymore.

I have copied the console output.

I would be happy, if someone could help me. I really need to program the FLASH. Is the FLASH broken after this accident. Would a replacement of the FLASH if I replaced it with a new one?

Kind Regards

 

Kerem OKTEM

 

 


cmd /C program_flash -f \
D:\ .... .sdk\FSBL\bootimage\BOOT.mcs \
-offset 0 -flash_type qspi-x4-single -fsbl \
D:\ .... .sdk\FSBL\Debug\FSBL.elf \
-blank_check -verify -cable type xilinx_tcf url TCP:127.0.0.1:3121 

****** Xilinx Program Flash
****** Program Flash v2019.1.3 (64-bit)
  **** SW Build 2644227 on Wed Sep  4 09:45:24 MDT 2019
    ** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.


WARNING: Failed to connect to hw_server at TCP:127.0.0.1:3121
Attempting to launch hw_server at TCP:127.0.0.1:3121

Connected to hw_server @ TCP:127.0.0.1:3121
Available targets and devices:
Target 0 : jsn-Arty Z7-003017A702C7A
    Device 0: jsn-Arty Z7-003017A702C7A-4ba00477-0

Retrieving Flash info...

Initialization done, programming the memory
===== mrd->addr=0xF800025C, data=0x00000001 =====
BOOT_MODE REG = 0x00000001
WARNING: [Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
===== mrd->addr=0xF8007080, data=0x30800100 =====
===== mrd->addr=0xF8000B18, data=0x80000000 =====
Downloading FSBL...
Running FSBL...
Finished running FSBL.
===== mrd->addr=0xF8000110, data=0x00177EA0 =====
READ: ARM_PLL_CFG (0xF8000110) = 0x00177EA0
===== mrd->addr=0xF8000100, data=0x0001A008 =====
READ: ARM_PLL_CTRL (0xF8000100) = 0x0001A008
===== mrd->addr=0xF8000120, data=0x1F000400 =====
READ: ARM_CLK_CTRL (0xF8000120) = 0x1F000400
===== mrd->addr=0xF8000118, data=0x00177EA0 =====
READ: IO_PLL_CFG (0xF8000118) = 0x00177EA0
===== mrd->addr=0xF8000108, data=0x0001A008 =====
READ: IO_PLL_CTRL (0xF8000108) = 0x0001A008
Info:  Remapping 256KB of on-chip-memory RAM memory to 0xFFFC0000.
===== mrd->addr=0xF8000008, data=0x00000000 =====
===== mwr->addr=0xF8000008, data=0x0000DF0D =====
MASKWRITE: addr=0xF8000008, mask=0x0000FFFF, newData=0x0000DF0D
===== mwr->addr=0xF8000910, data=0x000001FF =====
===== mrd->addr=0xF8000004, data=0x00000000 =====
===== mwr->addr=0xF8000004, data=0x0000767B =====
MASKWRITE: addr=0xF8000004, mask=0x0000FFFF, newData=0x0000767B


U-Boot 2019.01 (Jun 04 2019 - 09:48:11 -0600)

Model: Zynq CSE QSPI Board

DRAM:  256 KiB

WARNING: Caches not enabled

In:    dcc

Out:   dcc

Err:   dcc

Zynq> sf probe 0 0 0


Warning: SPI speed fallback to 100 kHz

SF: unrecognized JEDEC id bytes: ff, ff, 00

Failed to initialize SPI flash at 0:0 (error -2)

Zynq> ERROR: [Xicom 50-186] Error while detecting SPI flash device - unrecognized JEDEC id bytes: ff, ff, 00

Problem in running uboot
Flash programming initialization failed.

ERROR: Flash Operation Failed

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

@Kerem Oktem,

Will the flash work as a generic SPI flash instead of a QSPI flash?

Many of the QSPI flash devices on the market have special configuration registers within them.  These registers, if written, maintain their state across power cycles.  Some can only be written to once.  You may need to see if you can read them to find out what's going on.  Check out the chip you are using, then look into the configuration register settings to see if something got changed from its default.  You should be able to do this from SPI mode, although I've never used Xilinx's controller to necessarily know  how.

Dan

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...