J-Link Flash S32K144EVB-Q100 Unexpected core ID

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

    • J-Link Flash S32K144EVB-Q100 Unexpected core ID

      Hello,

      I recently purchased a J-Link and a S32K144EVB to start development with. When I tried to set up my J-Link Flash connection it gave me the message "Unexpected core ID." I have searched around and could not really find any information on this. Below is the output from J-Link Flash. Looking to see if I am doing something wrong or if I somehow need to change the expected Core ID the J-Link Flash expects.

      Application log started
      - J-Flash V6.52e (J-Flash compiled Oct 16 2019 12:17:45)
      - JLinkARM.dll V6.52e (DLL compiled Oct 16 2019 12:16:54)
      Creating new project ...
      - New project created successfully
      Connecting ...
      - Connecting via USB to J-Link device 0
      - J-Link firmware: J-Link V10 compiled Oct 8 2019 14:57:57
      - Device "S32K144" selected.
      - Target interface speed: 4000 kHz (Fixed)
      - VTarget = 5.025V
      - InitTarget()
      - TotalIRLen = 4, IRPrint = 0x01
      - JTAG chain detection found 1 devices:
      - #0 Id: 0x1993D01D, IRLen: 04, JTAG-DP
      - Scanning AP map to find all available APs
      - AP[2]: Stopped AP scan as end of AP map has been reached
      - AP[0]: AHB-AP (IDR: 0x24770011)
      - AP[1]: JTAG-AP (IDR: 0x001C0000)
      - Iterating through AP map to find AHB-AP to use
      - AP[0]: Core found
      - AP[0]: AHB-AP ROM base: 0xE00FF000
      - CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
      - Found Cortex-M4 r0p1, Little endian.
      - FPUnit: 6 code (BP) slots and 2 literal slots
      - CoreSight components:
      - ROMTbl[0] @ E00FF000
      - ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
      - ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
      - ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
      - ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
      - ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
      - Initializing 61440 bytes work RAM @ 0x1FFF8000
      - Reset: Halt core after reset via DEMCR.VC_CORERESET.
      - Reset: Reset device via AIRCR.SYSRESETREQ.
      - Executing init sequence ...
      - Initialized successfully
      - Target interface speed: 4000 kHz (Fixed)
      - WARNING: Unexpected core ID. (Found: 0x1993D01D, Expected: 0x4BA00477, Mask: 0x0F000FFF)
      - J-Link found 1 JTAG device. Core ID: 0x1993D01D (None)
      - Connected successfully


      I have noticed in another thread the S32K148 has a similar ID. Here is the excerpt for the post


      krzemyk wrote:

      Connecting to target via JTAG
      InitTarget()
      TotalIRLen = 4, IRPrint = 0x01
      JTAG chain detection found 1 devices:
      #0 Id: 0x0995001D, IRLen: 04, JTAG-DP
    • Hello,

      Thank you for your inquiry.
      We were not able to reproduce the warning with the EVB boards we got form NXP.
      However they have engineering samples on them so it is possible that these values have changed in the actually shipped cores.
      We will order additional boards from a more current batch and see how they compare.

      EDIT: Scratch that, we have one with a current production MCU and there it works as well.

      Do you see this issue with other EVB boards as well?
      Could you check your power supply to the target if it is stable 5V?
      Could you provide a screenshot of a J-Link Commander session?
      wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander

      The ID output by your target device looks completely wrong. The last 4 digits must be 0x0477 for Cortex-M.
      So either NXP made a huge mistake here or the ID is not transferred correctly to J-Link.
      How are you connecting to the target device? Are you using our official cables/adapters?
      segger.com/products/debug-prob…s/9-pin-cortex-m-adapter/


      Nonetheless the warning should not have impact on your Debug or Flash experience.

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

      I am out of the office today, but here are some of the answers to the questions.

      I only have 1 EVB to try currently and was just starting to play with it.

      I was able to dump the contents of the flash memory from it using J-Mem
      I have not tried to load/debug yet

      The target did say 5V, but I will provide a screen shot tomorrow of the J-link commander. It also had the ID of 0x1993D01D if I remember correctly

      I am using the official SEGGER 9 pin connector. I have a 19 pin connector as well

      I am connection to J14 on the EVB

      Thanks,
      CG
    • Hello,

      Thank you for your additional information.
      Unfortunately the behaviour was not reproducible on the boards we have in house so far.
      We will see if we can get our hands on other samples.

      Nontheless the message should in no way impact your debug experience and you can simply ignore it for now.
      Once we can reproduce the behaviour we will see how it could be fixed.

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