IMX RT1176 JTAG Debug fail.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMX RT1176 JTAG Debug fail.

Jump to solution
901 Views
Gyosun
Contributor III

Hello,

I created a custom board by referring to MIMXRT1170-EVKB.
The differences compared to EVKB are as follows.

MCU : MIMXRT1176DVMAA -> MIMXRT1176CVM8A
Flash : W25Q512NWEIQ -> W25Q128JVEIQ
DDR memory not used.

Unable to enter main() while loading using MCU-LINK-PRO.
I am attaching images captured when it is normal and when it is abnormal.
rt1176_pass.png 
rt1176_fail.png 

Thank you.
Best Regards,
Gyosun.

0 Kudos
Reply
1 Solution
856 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my name is Pavel, and I will be supporting your case, the example flexspi_nor_polling us the SFDP is a generic driver that is using to discover the majority of QSPI...

Pavel_Hernandez_0-1709935781991.png

If you want to create your own .cfx maybe this thread could help you.

How to create a new Flash driver of the MCUXPresso IDE - NXP Community

The other way you may need modify the FCB to correspond to your QSPI, and for that maybe this App note could help you, there is an explanation about the FCB.

Pavel_Hernandez_1-1709936061242.png

Boot from QSPI Flash on MIMXRT595-EVK (nxp.com)

Let me know if you have more questions about.

Best regards,
Pavel

View solution in original post

0 Kudos
Reply
3 Replies
882 Views
Gyosun
Contributor III

Hello,

After some more testing, I think I've figured out the cause.

After checking the "Link application to RAM" option, I connected JTAG and succeeded in booting the RAM.

After initializing Flash and reading the Vendor ID, 0xEF was read normally.

However, flexspi_nor_flash_erase_sector and flexspi_nor_flash_page_program do not seem to work properly.

FLASH changed from W25Q512NWEIQ to W25Q128JVEIQ, but things like 4-Byte Address Mode disappeared.

It appears that some commands have disappeared. How do I apply for W25Q128JVEIQ?

Thank you.
Best Regards,
Gyosun.

0 Kudos
Reply
857 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my name is Pavel, and I will be supporting your case, the example flexspi_nor_polling us the SFDP is a generic driver that is using to discover the majority of QSPI...

Pavel_Hernandez_0-1709935781991.png

If you want to create your own .cfx maybe this thread could help you.

How to create a new Flash driver of the MCUXPresso IDE - NXP Community

The other way you may need modify the FCB to correspond to your QSPI, and for that maybe this App note could help you, there is an explanation about the FCB.

Pavel_Hernandez_1-1709936061242.png

Boot from QSPI Flash on MIMXRT595-EVK (nxp.com)

Let me know if you have more questions about.

Best regards,
Pavel

0 Kudos
Reply
827 Views
Gyosun
Contributor III

Hi Pavel,

Thank you for your review.

The problem was resolved after modifying
the xif/evkbmimxrt1170_flexspi_nor_config.c file to match the flash used.
part: W25Q128JVEIQ

const flexspi_nor_config_t qspiflash_config = {
.sflashA1Size = 16u * 1024u * 1024u,
[0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xEB, RADDR_SDR, FLEXSPI_4PAD, 0x18),
[4 * 5 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x20, RADDR_SDR, FLEXSPI_1PAD, 0x18),
[4 * 9 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x2, RADDR_SDR, FLEXSPI_1PAD, 0x18),
}

Thank you,
Best Regards,
Gyosun.

0 Kudos
Reply