Error while reading netx90 flash

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

    • Error while reading netx90 flash

      Hello,

      i try to read the netx90 Flash with the J-Flash Tool. First i connect to the target:

      Source Code

      1. Application log started
      2. - J-Flash V6.50b (J-Flash compiled Sep 6 2019 17:58:12)
      3. - JLinkARM.dll V6.50b (DLL compiled Sep 6 2019 17:57:35)
      4. Creating new project ...
      5. - New project created successfully
      6. Connecting ...
      7. - Connecting via USB to J-Link device 0
      8. - J-Link firmware: J-Link Pro V4 compiled Aug 30 2019 09:21:29
      9. - Device "NETX90" selected.
      10. - Target interface speed: 4000 kHz (Fixed)
      11. - VTarget = 3.360V
      12. - TotalIRLen = 8, IRPrint = 0x0011
      13. - JTAG chain detection found 2 devices:
      14. - #0 Id: 0x6BA00477, IRLen: 04, CoreSight JTAG-DP
      15. - #1 Id: 0x10A046AD, IRLen: 04, Unknown device
      16. - Scanning AP map to find all available APs
      17. - AP[4]: Stopped AP scan as end of AP map has been reached
      18. - AP[0]: AHB-AP (IDR: 0x84770001)
      19. - AP[1]: APB-AP (IDR: 0x54770002)
      20. - AP[2]: AHB-AP (IDR: 0x24770011)
      21. - AP[3]: AHB-AP (IDR: 0x24770011)
      22. - Iterating through AP map to find AHB-AP to use
      23. - AP[0]: Skipped. No ROM table (AHB-AP ROM base: 0x00000002)
      24. - AP[1]: Skipped. Not an AHB-AP
      25. - AP[2]: Core found
      26. - AP[2]: AHB-AP ROM base: 0xE00FF000
      27. - CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
      28. - Found Cortex-M4 r0p1, Little endian.
      29. - FPUnit: 6 code (BP) slots and 2 literal slots
      30. - CoreSight components:
      31. - ROMTbl[0] @ E00FF000
      32. - ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB000 SCS
      33. - ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
      34. - ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
      35. - ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
      36. - ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
      37. - ROMTbl[0][6]: E0042000, CID: B105900D, PID: 005BB906 CTI
      38. - Executing init sequence ...
      39. - Initialized successfully
      40. - Target interface speed: 4000 kHz (Fixed)
      41. - J-Link found 2 JTAG devices. Core ID: 0x6BA00477 (None)
      42. - Connected successfully
      Display All

      After successful connection i tried to read back the Flash via Target --> Manual Programming --> Read Back --> Range



      Then I get an error message:


      Brainfuck Source Code

      1. Reading target memory (0x00100000 - 0x00102000) ...
      2. - Start of preparing flash programming
      3. - ERROR: PC of target system has unexpected value after checking target RAM. (PC = 0xE0A1E09C)!
      4. ---------------------------------------------------------------------- Registers -------------------------------------------------------------------------------------
      5. PC = E0A1E09C
      6. Current: R0 = 000202E0, R1 = 00020300, R2 = 00001000, R3 = 00000007
      7. R4 = 0004656A, R5 = 00106CD4, R6 = 00000000, R7 = 00139907
      8. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      9. - ERROR: Failed to prepare for programming.
      10. Failed to execute RAMCode for RAM check!
      11. - End of preparing flash programming
      12. - Start of restoring
      13. - End of restoring
      14. - ERROR: Failed to read back target memory
      15. Disconnecting ...
      16. - Disconnected
      Display All
      Why I can't read the flash from the netx90? What does this error mean?

      Furthermore I found out from another thread that the APP CPU is currently not supported:

      [SOLVED] Hilscher netx90 APP core dubugging

      Is the APP CPU planned for the future?

      Best Regards
      Johannes
    • Hi Johannes,
      Thanks for your inquiry.

      Recently there was a fix for this device.
      Could you please download the latest J-Link Software and Documentation Pack version and give it a try with that one?
      You can find it here:
      segger.com/downloads/jlink/#J-…twareAndDocumentationPack

      If this does not help:
      Are you using an evaluation board or custom hardware?
      If evaluation board: Which one(including revision)?
      If custom HW: Does this problem also occur on an evaluation board?

      Regarding the APP core:
      Once we have access to the documentation we will add support for this device.
      This is planned for sometime next year.

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

      Best regards,
      Fabian
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      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 Johannes,
      Sorry for the delay in response.

      We recently had a customer who had a similar problem.
      According to him the problem was caused by some switches on the evaluation board, which were not set correctly.
      Could you please check this?

      Did you contact Hilscher support?
      They might also know something about this.

      Best regards,
      Fabian
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      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.