Borrar filtros
Borrar filtros

Not able to dump hardware code from Simulink to F28379D launchpad

2 visualizaciones (últimos 30 días)
Neil
Neil el 12 de Abr. de 2024
Respondida: Raghava S N el 23 de Abr. de 2024
I have used Simulink to code F28379D launchpad (basic ePWM and ADC code) but after building and deploying it many times, it began showing this error and I could not deploy the code anymore. I guess the debug probe changed from XDS100v2 to XDS100v1 somehow but I don't know how to change it back.
Please suggest.

Respuestas (1)

Raghava S N
Raghava S N el 23 de Abr. de 2024
Hi Neil,
From your post, my understanding is that you are experiencing an issue with deploying code to the F28379D LaunchPad using Simulink, where the debug probe setting seems to have inadvertently changed from XDS100v2 to XDS100v1.
In the attached snapshot, the error you've encountered suggests two possible points of failure: a complication with the debug probe or a mismatch in the processor configuration. To address this accurately, it is essential to examine the target configuration file (*.ccxml), which has the necessary settings for your target, including both the debug probe and processor configurations.
To locate and verify the target configuration file in use by your model, please follow these instructions: Open your Simulink model and navigate via the Toolstrip to HARDWARE > Hardware Settings > Hardware Implementation > Target hardware resources > CCS hardware configuration file.
Thanks,
Raghava

Productos


Versión

R2022a

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by