Hi @Stephan_ ,
One point need to care, which is ignore previously, it is the flexSPI speed, please use the low speed test it, as the FlexSPI2 NOR secondary pin group doesn't offer DQS pad, so only support low-speed read.
So, please modify the code XIP:
1. app XIP
.seralClkFreq use 30Mhz, just for testing.
DQS loopback internally.
2. MCUbootUtility, please use this configuration to test:
3. Polling code
flexspi_device_config_t deviceconfig = {
.flexspiRootClk = 30000000,
.flashSize = FLASH_SIZE,
.CSIntervalUnit = kFLEXSPI_CsIntervalUnit1SckCycle,
.CSInterval = 2,
.CSHoldTime = 3,
.CSSetupTime = 3,
.dataValidTime = 0,
.columnspace = 0,
.enableWordAddress = 0,
.AWRSeqIndex = 0,
.AWRSeqNumber = 0,
.ARDSeqIndex = NOR_CMD_LUT_SEQ_IDX_READ_FAST_QUAD,
.ARDSeqNumber = 1,
.AHBWriteWaitUnit = kFLEXSPI_AhbWriteWaitUnit2AhbCycle,
.AHBWriteWaitInterval = 0,
};
Please use the low speed and test it again.
Any updated information, please kindly let me know.
best Regards,
kerry
Hi,
I'm actual in lab and had a close look at the QSPI signals. I can see MCU reading SFDP registers on normal SPI mode with 30MHz clock. Afterwards the status register 2 is read (also with 30MHz normal SPI), chip has onle the quad enabled flag 0x02 set. Up to this point all seems fine.
In the next step an XIP read array command (0xEB) is startet at address 0x001000. So MCU read IVT Table. This access is done with 60MHz as expected cos I've burned 'xSPI_FLASH_FREQ' fuses to value '6'. Strange thing here's that I can see data from flash after 8 dummy cycles but data will start with address 0x001004. According Adesto datasheet the flash has default 2 dummy cycles, so probably the chip sends first 4 bytes while MCU sends dummy cycles.
As you can see in below screenshots the data lines show 0xCD 24 00 as first data.
I've set the autoprobe fuse but propably the autoprobe failes due to slow SPI clock. I've try to set dummy cycles fix to 2 in fuses xSPI_FLASH_DUMMY_CYCLE to see if it helps, otherwise I start with next PCB on monday.
Best Regards
Hi,
I've tested the MCU Boot Utility with your settings, but without success. On Logic Analzyser I can see an Read Array command but with starting address 0x001000. The Flash response with data (but here I assume with 1 dummy cylce to mouch, data starts with 0x10 02 but should start with 0xD1 00 20). As you can see in screenshots below there is more or less valid data in QSPI lanes but in data showed in MCU Boot Utility has nothing in common.
I'll go on with changes in polling example.
Best Regards
Hi @Stephan_
So, your used flexSPI pin is not the same as the MIMXRT1170-EVK board, right?
As I know, the debugger download code to the flash also related to the program flashdirver, and this flashdriver will defines the related interface, different debugger the flashdriver file is not the same, I don't have your Lauterbach, so I don't know your related flashdriver code is using which interface.
Now, you can debug the code, I think you can try to download the simple code to the internal RAM, whehter that works, if that works OK, just the flash can't work, then I think still need to check your flash area.
Now, you connect to the flexSPI2 using the following interface?
In fact, when you don't familiar with the chip, we don't recommend you burn the fuse.
You also can try to modify this code and run it in the internal ram, whether your external flash works ok or not?
SDK_2_11_0_MIMXRT1170-EVK\boards\evkmimxrt1170\driver_examples\flexspi\nor\polling_transfer\cm7
You need to change the pinmux the related pin, and the interface, test this code at first.
Best Regards,
Kerry
Hi,
according Lauterbach support it should be possible to access QSPI flash at FlexSPI2.
Wr're using 2nd pin group, so correct tabel from TRM should be:
Actual I use a new hardware. Boot mode is set to 'Internal' and no fuses are burned.MCU start to 'Serial Download', I can connect using 'MCU Boot Utility'.
I've managed to change polling transfer example. Debug output shows "FLEXSPI example started!" and "Vendor ID: 0x1" (I think the AT25FF161A has vendor ID 0x1F). Call to function flexspi_nor_enable_quad_mode() won't return. I think there's still no connection to flash.
When I got it right there is no need to change fuse for 2nd pin group to this test, let me know if I had to.
Hello,
I try to answer your questions as good as possible
1 - We're using Adesto AT25FF161A which is quite simmilar to the AS25SF series.
2 - According Lauterbach Support the flash connection should working, but I'm on to clarify this in parallel.
3 - Here are the schematic part with flash connection. The CS wire is changed to CS0 on my board, actual PCB accidentally connected flash to CS1.
4 - I've added new pins in 'pin configuration' from MCUXpresso. Added used peripherals and updated code with MCUXpresso. Changed definitions EXAMPLE_FLEXSPI, XAMPLE_FLEXSPI_AMBA_BASE, EXAMPLE_FLEXSPI_CLOCK, FLASH_PORT to FlexSPI2. Changed configuration to run from RAM. Generated AXF file is loaded with Lauterbach Debugger. I've added modified project so you can diff it.
I hope this information helps to analyze the problem. If you need further information just let me know.
Best Regards
Stephan
Hi,
I've checked the clock MUX values, but according given documentation the value should be right:
Meanwhile Lauterbach Support was able to get flash working with uTrace Debugger. I've done some short tests and it seems to be working, so it looks like the problem is not located on PCB. I think there is still some modification missing in example project, but have no glue where...
Hi @Stephan_
Thanks for your updated information.
1. About the flexspi2 clock configuration, you are correct:
static inline void flexspi_clock_init(void)
{
/*Clock setting for flexspi1*/
CLOCK_SetRootClockDiv(kCLOCK_Root_Flexspi1, 2);
CLOCK_SetRootClockMux(kCLOCK_Root_Flexspi1, 0);
/*Clock setting for flexspi2*/
CLOCK_SetRootClockDiv(kCLOCK_Root_Flexspi2, 2);
CLOCK_SetRootClockMux(kCLOCK_Root_Flexspi2, 0);
}
/* Configure FLEXSPI2 using OSC_RC_48M_DIV2 */
rootCfg.mux = kCLOCK_FLEXSPI2_ClockRoot_MuxOscRc48MDiv2;
rootCfg.div = 1;
CLOCK_SetRootClock(kCLOCK_Root_Flexspi2, &rootCfg);
The API will help to configure the flexSPI2.
When you test the polling code, you run it in RAM?
2. Lauterbach Support was able to get flash working with uTrace Debugger
Please give me some debug screenshot, whether the flash address is correct? I mean, whether your code is downloaded to the external flash or not?
If it can download code to the flash, whether boot works or not after you modify the fuse:
1). FLEXSPI_INSTANCE fuse/boot pin is 1.
2). FLEXSPI_PIN_GROUP_SEL fuse bit is 0.
Best Regards,
Kerry
Hello,
my test programm is running in RAM, I've use the setting you described in screenshot.
According the flashed code, when try to run from flash I use 'release' configuration in MCUXpresso. With Lauterbach I load axf file which write program code to flash. When I dump the first addresses from flash it look like this:
I've set fuses as follows:
We're using 2nd pin group, so there is FLEXSPI_PIN_GROUP_SEL set to 1.
I've opened another thread about generation bootable binary file (Create bootable image for RT1173 QSPI flash - NXP Community), so I think we can stick to 'run from RAM' configuration and try to get polling example working.
Hi @Stephan_
1. Seems your Lauterbach already enter the debug mode, please run it directly.
Then check the printf information, whether the external QSPI flash runs OK or not?
You can see the printf information through the UART interface.
GPIO_AD_25->LPUART1_RXD
GPIO_AD_24->LPUART1_TXD
2. MCUBootUtlity, seems you also connect to the chip, please select bootDevice Memory
In the Boot Device Memory, you can readout the memory.
In the connection area, you can select One Step to connect your board.
Best Regards,
Kerry
Hi @Stephan_ ,
Thanks for your information, as I don't have the RT1170 board which connect the QSPI in the flexSPI2, so I can't test it direct.
Now, seems only your debugger Lauterbach can download the code, but I find your downloaded code is not correct, it didn't contains the FCB, IVT, so the image is totally wrong, could you please use my attached led_blinky and test it with your Lauterbach?
My image is correct:
From 0X600004000 FCB:
0X60001000 IVT:
From 0X60002000, app:
Please use your debugger test my .axf, whether the led code function works or not? Test it in the internal boot mode directly.
Any updated information, kindly let me know.
Best Regards,
Kerry
