- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- MCUXpresso Training Hub
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- Product Forums
- :
- MPC5xxx
- :
- mpc5744&&multi debugger problem
mpc5744&&multi debugger problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
mpc5744&&multi debugger problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Experts:
Our current project is to integrate EB's osek protocol stack (communication, network management, diagnosis) based on mcal. After the integration, the program will enter the abnormal interrupt during the running, and the internal watchdog cannot reset the microcontroller.
It has now been found that there are two situations in which an exception will be entered:
- The first run after each use of the debugger flash program, enter machine_check_int_ha when running to fccu configuration. How should I go to troubleshoot the problem? After resetting the program with the debugger, the program can run normally temporarily, but the second case will be encountered.
- The current controller is configured with Rx messages of about 10 frames. If the controller only sends out, the program can run normally for a long time; use CANoe to simulate all Rx messages sent to the controller, and the program will enter the exception after running for several tens of seconds.
After the program enters the exception, the greenhills probe debugger we are using cannot get the value of the exception register, so there is no way to check the cause of the exception.
A separate mcal program (without network management and diagnostics) has been tested and has not experienced an exception when accepting messages. EB's osek protocol stack itself is not based on the mcal program. They can only test their own programs to see if they can see the same phenomenon.
Best and Regards
Orion
