- 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
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- 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
-
- 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
- RFID / NFC
-
- Home
- :
- Model-Based Design Toolbox (MBDT)
- :
- Model-Based Design Toolbox (MBDT)
- :
- Re: MPC5777c loss of communication for ccp mcu
MPC5777c loss of communication for ccp mcu
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am facing an issue while flashing software from Simulink/Matlab via bootloader for the MPC5777C-DEVB board.
I get the error Loss of communication for CCP MCU. (attached screenshot)
I did setup according to Model_Based_Design_Toolbox_MPC57xx_Series_Quick_Start_Guide.pdf documentation.
I tried flash with two files via S32DS:
1. MPC5777C_S32DS_UART0_CAN0.srec
2. MPC5777C_S32DS_UART2_CAN0.rbf
And in advanced options for Flash algorithm selection, i used alternative algorithm option and set to"nxp_mpc5777c_1x32x64k_eeprom.pcp"
I get the same error while flashing via bootloader "Loss of Communication for CCP MCU"
Please help me with right solution for this problem.
Thank you.
Abhinand D
Solved! Go to Solution.
mariuslucianand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @abhinand_rd ,
the FTDI chip is connected to the RXDA/TXDA. So the rbf with the UART0 should do the job. It looks to me that you've followed the right steps.
Just to be sure that you are using the right settings. Please check in the model to have the Boot Assist Module Restart Request checked. This check box will give you a message, once the code has been successfully compiled, asking you to reset the board. At that moment, please press the reset button on the board and press ok. This will force the board to enter bootloader and wait for the program on the UART.
If the restart checkbox did not work, let's check the USB connection. For that, please generate code for the uart_hello_world_mpc5777C model. Inside the folder next to the mdl you will find an elf file. Please flash that elf file (using standard algorithm this time, not the nxp_mpc5777c_1x32x64k_eeprom.pcp. This pcp file should be used only with the bootloader).
By flashing the generated elf file from the uart_hello_world_mpc5777C we can check the UART connection. If the connection is working, you can try again to reflash the bootloader and to start deployment via UART.
Hope this helps,
Marius
mariuslucianand
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @abhinand_rd ,
the FTDI chip is connected to the RXDA/TXDA. So the rbf with the UART0 should do the job. It looks to me that you've followed the right steps.
Just to be sure that you are using the right settings. Please check in the model to have the Boot Assist Module Restart Request checked. This check box will give you a message, once the code has been successfully compiled, asking you to reset the board. At that moment, please press the reset button on the board and press ok. This will force the board to enter bootloader and wait for the program on the UART.
If the restart checkbox did not work, let's check the USB connection. For that, please generate code for the uart_hello_world_mpc5777C model. Inside the folder next to the mdl you will find an elf file. Please flash that elf file (using standard algorithm this time, not the nxp_mpc5777c_1x32x64k_eeprom.pcp. This pcp file should be used only with the bootloader).
By flashing the generated elf file from the uart_hello_world_mpc5777C we can check the UART connection. If the connection is working, you can try again to reflash the bootloader and to start deployment via UART.
Hope this helps,
Marius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have encountered same problem with my s32k144 mcu. Please give me solution
