Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug Setup Instructions for I-Jet #83

Open
sm-github-work opened this issue May 13, 2020 · 1 comment
Open

Debug Setup Instructions for I-Jet #83

sm-github-work opened this issue May 13, 2020 · 1 comment

Comments

@sm-github-work
Copy link

sm-github-work commented May 13, 2020

This is a feature request for debugger setup instructions for I-Jet probes.

I looked at the instructions at: https://iar-vsc.readthedocs.io/en/latest/pages/user_guide.html#debugging

I was hoping for more detailed setup instructions for IAR's I-jet probes. Does IAR provide a gdb server or do you need to use the Arm Embedded GNU Tools?

The only thing I could find on IAR's site (https://www.iar.com/support/user-guides/user-guide-iar-embedded-workbench-for-arm/) was this page: http://ftp.iar.se/WWWfiles/arm/webic/doc/infocenter/gdbserv_quickstart.html that mentions OpenOCD, but didn't have enough detail to be helpful.

ST has a fairly detailed guide for the ST-Link [pdf warning]: https://www.st.com/resource/en/user_manual/dm00613038-stm32cubeide-stlink-gdb-server-stmicroelectronics.pdf

@spoorcc
Copy link
Contributor

spoorcc commented May 18, 2020

For cortex debugging I reguraly use the cortex-debug plugin (https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug). It has both support for openocd and the Arm embedded GNU tools. Especially the register view is great. Both the segger j-link and the stlink work for me. I don't have any experience with gdb/openocd and the I-jet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants