Code flashing error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Code flashing error

Jump to solution
326 Views
embedded12
Contributor I

Hello,

I am working with the RDBESSK358BMU (S32K358) using S32 Design Studio 3.6.4 and RTD drivers. I am attempting to run a simple Dio example to toggle the onboard LED to confirm MCU operation.

The project builds, flashes, and verifies successfully via the PEmicro debugger, and the device resets without errors. Breakpoints indicate that the application reaches main() and executes normally. However, LED D does not blink or change state, even when toggling output polarity and using long delays.

I configured the GPIO pin in the project’s .mex file and regenerated code, but the generated configuration files do not appear to reflect the pin changes, even after cleaning and rebuilding the project. currently the example uses PTA0 which doesnt look for my board

Could you please advise on:

  • The correct GPIO pin mapping for LED D on this board 

  • Why .mex configuration changes may not propagate to generated files

Tags (1)
0 Kudos
Reply
1 Solution
298 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @embedded12 

If you refer to the description.txt file included with the example, you will see that it states the example supports only the S32K3X8EVB‑Q289. This hardware is not compatible with the RDK358BMU board. There are several hardware differences between the two boards, so running any example on your board will require taking the differences into account and modifying as needed. It will not be a plug‑and‑play experience as it would be when using the EVB.

I recommend reviewing the board schematic to better understand the board’s connections and how it interacts with the other devices.

Regarding the changes made in the .mex file not being reflected in the generated files, could you please share screenshots of what you are observing? Also, which RTD version are you using so I can verify the behavior on my side?

 

BR, VaneB

View solution in original post

0 Kudos
Reply
1 Reply
299 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @embedded12 

If you refer to the description.txt file included with the example, you will see that it states the example supports only the S32K3X8EVB‑Q289. This hardware is not compatible with the RDK358BMU board. There are several hardware differences between the two boards, so running any example on your board will require taking the differences into account and modifying as needed. It will not be a plug‑and‑play experience as it would be when using the EVB.

I recommend reviewing the board schematic to better understand the board’s connections and how it interacts with the other devices.

Regarding the changes made in the .mex file not being reflected in the generated files, could you please share screenshots of what you are observing? Also, which RTD version are you using so I can verify the behavior on my side?

 

BR, VaneB

0 Kudos
Reply