NXP MPC5748 FreeRTOS demo

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

NXP MPC5748 FreeRTOS demo

1,060 Views
Mina_Sameh_26
Contributor I

we are testing FreeRTOS on the NXP MPC5748G by running the ready made demo provided by S32 design Studio it works fine when we Build and run the project but when we try to build and run the project as a standalone project the project main functionality does not run as intended after some trace we found that the problem is most likely to be in vtaskdelay() is not working so please can anyone suggest a solution

0 Kudos
Reply
1 Reply

822 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

It sounds like your FreeRTOS tick isn’t running in the “standalone” build, so vTaskDelay() never wakes tasks. On the MPC5748G (PowerPC e200z4), that typically boils down to one of these in the move from “Run in IDE” → “Run from flash/standalone”:

  • Clock source isn’t actually configured (PLL not locked, bus clock different).
  • The tick timer isn’t initialized or its interrupt isn’t firing (STM/PIT/RTI).
  • Global interrupts aren’t enabled (MSR.EE = 0).
  • The interrupt vector table (IVPR) isn’t placed or the INTC isn’t set up in standalone.
  • Interrupt priorities conflict with FreeRTOS’s configMAX_SYSCALL_INTERRUPT_PRIORITY.
  • Linker/startup differences (missing startup code or wrong section placement).
  • Watchdog resetting before you notice.

Best regards,

Peter

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2266357%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ENXP%20MPC5748%20FreeRTOS%20demo%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2266357%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3Ewe%20are%20testing%20FreeRTOS%20on%20the%20NXP%20MPC5748G%20by%20running%20the%20ready%20made%20demo%20provided%20by%20S32%20design%20Studio%20it%20works%20fine%20when%20we%20Build%20and%20run%20the%20project%20but%20when%20we%20try%20to%20build%20and%20run%20the%20project%20as%20a%20standalone%20project%20the%20project%20main%20functionality%20does%20not%20run%20as%20intended%20after%20some%20trace%20we%20found%20that%20the%20problem%20is%20most%20likely%20to%20be%20in%20vtaskdelay()%20is%20not%20working%20so%20please%20can%20anyone%20suggest%20a%20solution%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2270742%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20NXP%20MPC5748%20FreeRTOS%20demo%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2270742%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3EIt%20sounds%20like%20your%20FreeRTOS%20tick%20isn%E2%80%99t%20running%20in%20the%20%E2%80%9Cstandalone%E2%80%9D%20build%2C%20so%20vTaskDelay()%20never%20wakes%20tasks.%20On%20the%20MPC5748G%20(PowerPC%20e200z4)%2C%20that%20typically%20boils%20down%20to%20one%20of%20these%20in%20the%20move%20from%20%E2%80%9CRun%20in%20IDE%E2%80%9D%20%E2%86%92%20%E2%80%9CRun%20from%20flash%2Fstandalone%E2%80%9D%3A%3C%2FP%3E%0A%3CDIV%3E%0A%3CUL%3E%0A%3CLI%3EClock%20source%20isn%E2%80%99t%20actually%20configured%20(PLL%20not%20locked%2C%20bus%20clock%20different).%3C%2FLI%3E%0A%3CLI%3EThe%20tick%20timer%20isn%E2%80%99t%20initialized%20or%20its%20interrupt%20isn%E2%80%99t%20firing%20(STM%2FPIT%2FRTI).%3C%2FLI%3E%0A%3CLI%3EGlobal%20interrupts%20aren%E2%80%99t%20enabled%20(MSR.EE%20%3D%200).%3C%2FLI%3E%0A%3CLI%3EThe%20interrupt%20vector%20table%20(IVPR)%20isn%E2%80%99t%20placed%20or%20the%20INTC%20isn%E2%80%99t%20set%20up%20in%20standalone.%3C%2FLI%3E%0A%3CLI%3EInterrupt%20priorities%20conflict%20with%20FreeRTOS%E2%80%99s%20configMAX_SYSCALL_INTERRUPT_PRIORITY.%3C%2FLI%3E%0A%3CLI%3ELinker%2Fstartup%20differences%20(missing%20startup%20code%20or%20wrong%20section%20placement).%3C%2FLI%3E%0A%3CLI%3EWatchdog%20resetting%20before%20you%20notice.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3EPeter%3C%2FP%3E%3C%2FLINGO-BODY%3E