[SOLVED] Renesas EK-RA6M4 Board and problem with chip programming/erase/read back

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

  • [SOLVED] Renesas EK-RA6M4 Board and problem with chip programming/erase/read back

    Hello,

    I am using J-Trace PRO Cortex M for interfacing with Renesas EK-RA6M4 board.
    I have a problem and I hope so that you can help me.

    Currently I am unable to program or erase or readback chip content.

    Hardware setup:
    I have Renesas development board EK-RA6M4
    renesas.com/us/en/products/mic…ation-kit-ra6m4-mcu-group

    with R7FA6M4AF3CFB uC, Cortex M33 core.


    This board has Jlink Onboard Debugger that works for debugging from Renesas E2 studio. Connection is SWD.


    Since I have a need to use J-Trace for development and J-LINK Plus later for production programming of these microcontrollers, I have a need to use JFlash.exe and Jlink Onboard Debugger is not applicable for that use case.

    When I try to program or erase uC with external debugger I receive error in JFlash.
    J-Trace PRO Cortex M is recently bought so it does support uC, per guideline on link: wiki.segger.com/RA6M4#Tracing_on_Renesas_R7FA6M4

    Example project from aforementioned link "Example Project: Renesas_R7FA6M4_TraceBuffer.zip " works successfully from Ozone. I am able to have trace functionality and it is a sign that connection is good between
    J-Trace PRO and target uC. I should mention that jumpers on evaluation board are setup for usage of external debugger.


    However, if I try to use J flash for programming/erasing or read back i have this error:


    J Flash console log is:

    Source Code

    1. Application log started
    2. - J-Flash V6.94 (J-Flash compiled Jan 8 2021 13:01:52)
    3. - JLinkARM.dll V6.94 (DLL compiled Jan 8 2021 13:01:30)
    4. Reading flash device list [C:\Program Files (x86)\SEGGER\JLink\ETC/JFlash/Flash.csv] ...
    5. - List of flash devices read successfully (451 Devices)
    6. Reading MCU device list ...
    7. - List of MCU devices read successfully (8230 Devices)
    8. Creating new project ...
    9. - New project created successfully
    10. Connecting ...
    11. - Connecting via USB to probe/ programmer device 0
    12. - Probe/ Programmer firmware: J-Trace PRO V2 Cortex-M compiled Jan 4 2021 16:19:11
    13. - Device "R7FA6M4AF" selected.
    14. - Target interface speed: 4000 kHz (Fixed)
    15. - VTarget = 3.322V
    16. - InitTarget() start
    17. - Determining TrustZone configuration...
    18. - Secure Debug: Enabled (SSD)
    19. - Determining currently configured transfer type by reading the AHB-AP CSW register.
    20. - --> Correct transfer type configured. Done.
    21. - InitTarget() end
    22. - Found SW-DP with ID 0x6BA02477
    23. - DPIDR: 0x6BA02477
    24. - Scanning AP map to find all available APs
    25. - AP[2]: Stopped AP scan as end of AP map has been reached
    26. - AP[0]: AHB-AP (IDR: 0x84770001)
    27. - AP[1]: APB-AP (IDR: 0x54770002)
    28. - Iterating through AP map to find AHB-AP to use
    29. - AP[0]: Core found
    30. - AP[0]: AHB-AP ROM base: 0xE00FE000
    31. - CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
    32. - Found Cortex-M33 r0p4, Little endian.
    33. - FPUnit: 8 code (BP) slots and 0 literal slots
    34. - Security extension: implemented
    35. - Secure debug: enabled
    36. - CoreSight components:
    37. - ROMTbl[0] @ E00FE000
    38. - ROMTbl[0][0]: E0044000, CID: B105900D, PID: 005BB906 CTI
    39. - ROMTbl[0][1]: E0047000, CID: B105900D, PID: 003BB908 CSTF
    40. - ROMTbl[0][2]: E0048000, CID: B105900D, PID: 001BB961 TMC
    41. - ROMTbl[0][3]: E0049000, CID: B105F00D, PID: 001BB101 TSG
    42. - ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BBD21 Cortex-M33
    43. - ROMTbl[0][5]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table
    44. - ROMTbl[1] @ E00FF000
    45. - ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
    46. - ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
    47. - ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
    48. - ROMTbl[1][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
    49. - ROMTbl[1][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
    50. - ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
    51. - Executing init sequence ...
    52. - Executing Reset (0, 0 ms)
    53. - Initialized successfully
    54. - Target interface speed: 4000 kHz (Fixed)
    55. - CPU clock frequency: 2072 kHz (Auto detected)
    56. - Found 1 JTAG device. Core ID: 0x6BA02477 (None)
    57. - Connected successfully
    58. Reading entire flash chip ...
    59. - 199 sectors, 4 ranges, 0x0 - 0xFFFFF, 0x100A100 - 0x100A2FF, 0x8000000 - 0x8001FFF, 0x60000000 - 0x63FFFFFF
    60. - ERROR: Unknown flash algo type @ addr. 0x0100A100. Algorithm ignored.
    61. - ERROR: Failed to read back target memory
    62. Disconnecting ...
    63. - Disconnected
    Display All
    Is some additional setup needed for J Flash in order to work correctly with the uC?

  • Hello,

    For RA6M4, the J-Link software has to use a very device specific method due to the security extensions.
    Right now, this method is supported via J-Link Commander, only. J-Flash will follow within the next few weeks.

    Stay up-to-date regarding J-Link:
    segger.com/notification/subscribe.php?prodid=7,94

    Sorry for any inconveniences caused.

    Best regards,
    Erik
    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.