Hi,

we are developing some projects with NXP RT106x processors and are using a QSPI flash.

We are having troubles with latest Ozone / JLink updates.
Currentrly we are using Ozone 3.10e with J-Link 6.62b, which are working fine.

We noticed that RT106x processors are not listed anymore in JLinkDevices.xml (JLink in Ozone 3.20b).

Our project uses a Winbond W25Q128JVSIM flash, QSPI, secondary pinmux.
What happened a few times is that after some download fails with Ozone 3.20b,
we were unable to clear the flash content with J-Flash (erase chip).
Using NXP Boot Utility we found that probably the boot header got corrupted since
it showed occasionally a zero sector size of the flash.

Best regards,
Alessio

Hi,

we need to start from the ROM bootloader so we already had the .jdebug file modified,
however AfterTargetDownload() and AfterTargetReset() were commented out.
I fixed the .jdebug file leaving AfterTargetDownload() and AfterTargetReset() empty, but it doesn't seems to help.

These are the steps I tried with the correct .jdebug project:
- J-Flash 6.62b -> Erase Chip (completed successfully) -> Disconnect
- Ozone 3.10e -> F5
download ok, halt at main()
- Stop
- F5
download ok, halt at main()
- Stop
- J-Flash 6.62b -> Erase Chip (completed successfully) -> Disconnect
- Ozone 3.20b -> F5
error:
Programming failed @ address 0x60000014 (block verification error)
Download failed: error during program/erase phase
halting the program stops at 0x0021AA58
- Stop
- F5
error:
Failed to prepare RAMCode using RAM
Error while determining flash info (Bank @ 0x60000000)
Download failed: J-Link reports an unspecified download error
- Stop
- J-Flash 6.62b -> Erase Chip
fail:
Erasing chip ...
- Connecting ...
- Connected successfully
- 128 sectors, 1 range, 0x60000000 - 0x607FFFFF
- Start of determining flash info (Bank 0 @ 0x60000000)
- End of determining flash info
- Flash bank info:
- 128 * 64 KB @ 0x60000000
- Start of preparing flash programming
- End of preparing flash programming
- Start of determining dirty areas in flash cache
- End of determining dirty areas
- CPU speed could not be measured.
- Chip erase not supported for flash bank @ 0x60000000. Switched to sector erase
- Start of determining dirty areas in flash cache
- End of determining dirty areas
- Start of erasing sectors
- Erasing range 0x60000000 - 0x6001FFFF ( 2 Sectors, 128 KB)
- ERROR: Failed to erase sectors.
- End of erasing sectors
- ERROR: Erase failed
- Start of restoring
- End of restoring
- ERROR: Failed to erase chip
Disconnecting ...
- Disconnected
now the bad flash state is triggered and we are unable to erase the flash content anymore.

Best regards,
Alessio

Hi,
installing the latest JLink version (6.80e) and updating the Ozone 3.20b dll seems to solve the problem.
The application now start and halt at main().

Thanks,
Alessio