STLINK-V3SET connection to OSD32MP157C using CubeProgrammer

This topic has 6 replies, 2 voices, and was last updated 1 year, 10 months ago by Neeraj Dantu.

Viewing 6 reply threads

Author
Posts
- January 2, 2023 at 11:26 am #13015
  gil_he
  Participant
  hello,
  I am connecting the OSD32MP157C (in our project) to the STLINK-V3SET debugger using the debugger STDC14 CN1 connector.
  The CubeProgrammer is configured for JTAG.
  I assume the pin/signal direction, with regard to the debugger, for the following, is:
  Pin 4, T_JTMS – out
  Pin 6, T_JCLK – out
  Pin 8, T_JTDO – in
  Pin 10, T_JTDI – out
  I connected the JTDI of the SoC to the T_JTDI of the debugger. Same with JTDO, JTCK and JTMS.
  I am also providing 3.3V to pin 3, T_VCC and of-course connecting the GND pins.
  I am not connecting OSD32MP NJTRST pin to pin 12, T_NRST in the debugger (the STM32MP has an internal PU on it).
  I understand, according to JTAG, this pin is optional.
  The connection fails using the CubeProgrammer.
  I get the following message: “ST-LINK error (DEV_UNKNOWN_MCU_TARGET)”.
  On another board of ours, I get: “Error: No STM32 target found!”.
  On the debugger the PWR led lights green and the COM led lights red.
  The STM32MP157C boot mode is JTAG.
  The SiP receives TCK/TMS/TDI signals (activity is there) but sends no response on the TDO pin.
  What am I missing here?
  
  thanks
  Gil
  - This topic was modified 1 year, 10 months ago by gil_he.
  - This topic was modified 1 year, 10 months ago by Greg Sheridan.
- January 5, 2023 at 9:00 am #13043
  gil_he
  Participant
  An update:
  I connected the debugger (STLINK-V3SET) to the Octavo RED.
  Also added the NRST and NJRST signals from the RED to the Debugger (pins 12 and 11 respectively).
  Still, no response.
  The CubeProgrammer doesn’t recognize the Octavo SiP.
  - This reply was modified 1 year, 10 months ago by gil_he.
- January 5, 2023 at 11:56 am #13046
  Neeraj Dantu
  Moderator
  Gil,
  As communicated offline, please see below:
  1. Make sure all the jumpers required for the STLink V3 are populated according to the user guide: https://www.st.com/resource/en/user_manual/um2448-stlinkv3set-debuggerprogrammer-for-stm8-and-stm32-stmicroelectronics.pdf
  2. Make sure you can connect to the debugger. You may need to upgrade CubeIDE to get latest drivers.
  3. Make sure the debugger configuration for the CubeIDE project is correct and that STLink probe is detected and selected in the debug configuration window for the project.
  We have verified connecting OSD32MP1-RED with STLink-V2 and STLink-V3 should not be any different. If you have an ST EV1 board, can you can connect the signals the exact same way as you are connecting to OSD32MP1-RED and verify the behavior is different.
  Please let us know how it goes.
  Best,
  Neeraj
- January 6, 2023 at 5:46 am #13049
  gil_he
  Participant
  hello Neeraj,
  I verified your comments.
  All is, as required.
  I am using STM32cubeProgrammer as stand-alone (not part of CubeIDE).
  Installed the latest software. I hope it installs the latest drivers.
  Still, no response from the debugger.
  
  We don’t have a ST EV1.
  Can you verify the RED and STLINK-V3 communicate in your lab?
  In our lab they don’t.
  
  I compared the signals the debugger send to the RED and to our project. They are very much alike.
  J_TDO has no activity.
  
  thanks
  Gil
  - This reply was modified 1 year, 10 months ago by gil_he.
- January 10, 2023 at 5:30 pm #13240
  Neeraj Dantu
  Moderator
  Gil,
  I have verified STLink V3 with OSD32MP1-RED(with CubeIDE). I suggest installing CubeIDE, which may give you more detail on the error. Please double check the settings, I used the tag-connect header on OSD32MP1R-RED with Engineering mode(you will need to use 0b100 boot mode for this, make sure you have this boot mode), ST-LINK OpenOCD, Connection setup in CubeIDE is SWD interface, 8MHz frequency.
  Best,
  Neeraj
- January 12, 2023 at 6:08 am #13273
  gil_he
  Participant
  hello Neeraj,
  I was able to connect the RED to the debugger using SWD.
  I need to perform some wire stitching before I can connect our board to the debugger using SWD.
  My question:
  Can we use the CubeIDE to debug the FSBL load/run process via SWD connection?
  Can you guide me on what should be done?
  thanks
  Gil
  - This reply was modified 1 year, 10 months ago by gil_he.
- January 17, 2023 at 1:04 pm #13312
  Neeraj Dantu
  Moderator
  Gil,
  You should be able to do TF-A debug with CubeIDE, but there is currently no tutorial to show how it is done. However, you can use gdb as shown here: https://wiki.st.com/stm32mpu/wiki/How_to_debug_TF-A_BL2
  Best,
  Neeraj
  EDIT: Found this: https://wiki.st.com/stm32mpu/wiki/How_to_manage_OpenSTLinux_projects_in_STM32CubeIDE. You can use CubeIDE to load OpenSTLinux projects.
  - This reply was modified 1 year, 10 months ago by Neeraj Dantu.
Author
Posts

Viewing 6 reply threads

You must be logged in to reply to this topic.