Cannot get Cube Monitor to connect to STM32G431CB on |BG431B-ESC1 board - not connected ! Unknown JTAG chain (16)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-05-28 8:04 AM
I have successfully built and downloaded the motor control application using ST motor control workbench and the CubeIDE etc and can connect to flash and step through my program. However when it comes to using CubeMonitor i get an error giving "not connected ! Unknown JTAG chain (16)"
In the config screen i can flash the LED on the board ...
I have tried both protocols SWD and and JTAG .. Can i use monitor with the BG431B-ESC1 board ?
Many thanks if youve got this far ....
Solved! Go to Solution.
- Labels:
-
STM32CubeMonitor
-
STM32G4 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-06-02 4:07 AM
Ha actually I fixed this by deleting and re-adding the the send and receive nodes and configuring as SWD protocol...!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-06-02 1:52 AM
Hello ChrissyP,
Thank you for reporting this issue,
This error should only happen when the board is not supporting JTAG.
Can you tell me if the error is the same when testing in SWD and JTAG modes, i.e. 0xF6 ( Unknown JTAG chain) in both cases.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-06-02 4:01 AM
Yes i get (F6) irrespective of the selected protocol...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-06-02 4:07 AM
Ha actually I fixed this by deleting and re-adding the the send and receive nodes and configuring as SWD protocol...!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-06-02 5:12 AM
Good, thank you for your feedback
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-06-02 7:08 AM
In order to double check, can you please, with your configuration, move back to JTAG protocol , check the error is still there and then move back to SWD and check it's OK (don't forget to press DEPLOY button in between).
I just want to be sure you're not in a config where CubeMonitor does take protocol change into account by mistake.
