[SOLVED] Ozone 3.20b / JLink 6.80 problems with RT106x processors and QSPI flash

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Ozone 3.20b / JLink 6.80 problems with RT106x processors and QSPI flash

    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
  • Hello Alessio,


    ballotz wrote:

    We noticed that RT106x processors are not listed anymore in JLinkDevices.xml (JLink in Ozone 3.20b).
    Yes this is intended behaviour as the QSPI flash loader is now compiled into the J-Link dll.


    ballotz wrote:

    Using NXP Boot Utility we found that probably the boot header got corrupted since
    it showed occasionally a zero sector size of the flash.
    Did you adjust your Ozone project as explained in your other thread?
    Missing RAM functions from Execution Profile

    Does it work then?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • 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
  • Hello Alessio,

    Could you give the latest J-Link software a try so we are not hunting some already fixed issues here?
    segger.com/downloads/jlink/#J-…twareAndDocumentationPack

    Do you see the same behaviour?

    EDIT:

    ballotz wrote:

    Our project uses a Winbond W25Q128JVSIM flash, QSPI, secondary pinmux.
    What does secondary pin mux mean here?
    Is it the same like on the NXP MIMXRT1060-EVK eval board?

    If not this would explain the behaviour as the flash loader will only work with exactly that configuration.
    For other configurations a new flash loader must be created.


    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Alessio,

    Great to hear that you are up and running again.

    We will consider this thread a solved now.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.