Ozone STM32MP1 Coprocessor debugging

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

    • Ozone STM32MP1 Coprocessor debugging

      Hi there,
      I am trying to debug the Cortex-M4 coprocessor of a STM32MP1 multi-core micro using Ozone, but connecting to target fails. Here is the console output:

      Debug.Start();
      Device "STM32MP15XX_M4_DUALFLASH" selected.
      ConfigTargetSettings() start
      ConfigTargetSettings() end
      InitTarget() start
      J-Link script: InitTarget()
      InitTarget() end
      TotalIRLen = 9, IRPrint = 0x0011
      JTAG chain detection found 2 devices:
      #0 Id: 0x6BA00477, IRLen: 04, CoreSight JTAG-DP
      #1 Id: 0x06500041, IRLen: 05, Unknown device
      Failed to power up DAP

      I did setup an empty Ozone project with a simple "Hello World" program and selected the "STM32MP15xx_m4_dualflash" as device, but it seems that I missed something... Does anyone can tell me the correct settings for accessing the M4 core insight the STM32MP1?

      ~Karsten
    • Hello Karsten,

      Thank you for your inquiry.
      Are you using custom hardware or an eval board?
      You can find an example project for the STM32MP15X-EVAL on our Wiki:
      wiki.segger.com/STM32MP15x#Tracing_on_STM32MP15x

      Could you give the TMC/ETB trace sample a try?

      Does it work for you as well?


      If not could you check the following troubleshooting steps and provide a screenshot of the Commander session?

      wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection

      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.