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

Support for Tiva-C Launchpad TM4C123GXL development board #15

Open
UdayakumarHidakal opened this issue Mar 30, 2022 · 2 comments
Open

Comments

@UdayakumarHidakal
Copy link

Hello,
I am working on TM4C123GXL development board, here i am able to blink led,
But i am unable to debug the things regarding flash writing/erasing, also which is not available in probe-run list.

So please let me know is this repository stops working or not ?

@sbourdeauducq
Copy link
Member

sbourdeauducq commented Mar 30, 2022

It definitely works well enough to blink LEDs, though it wasn't tried on that board. You may have some homework to do.

@amcelroy
Copy link
Contributor

This repository works. We use it with the latest TM4C123 chips (our own PCB and Launchpads) in combination with the tm4c-hal and RTIC 0.5.

Debugging a stock Launchpad is challenging due to TI wanting us to use Stellaris and their Code Composer Studio, but you can use a Segger debugger by connecting the unsoldered debug pins on the the Launchpad to the Segger, typically using a breakout board. We use VS Code, Segger, some various plugins, and ultimately the Segger GDB program bundled with the JLink tools. If you download the .SVD file and configure the VS Code plugins correctly, you can view peripheral addresses and inspect registers also.

There is a way to use a 2nd Launchpad to flash the target Launchpad using OpenOCD and the debug pin headers that a colleague used initially, but I think the Segger + Breakout Board is a much more intuitive way to interact with the MCU.

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

3 participants