RM44L520: Halcogen bug - RM44L520PGE_FREERTOS

Audun Knudsrod

Part Number: RM44L520
Other Parts Discussed in Thread: HALCOGEN

Hi!

I think the HALCoGen FreeRTOS template for chip RM44L520PGE is wrong.

Update: Most of my issues were related to my own project configurations.
Problem
On my system the timing is all arbitrary, e.g. the ECLK signal is unstable.

Edit: The PINMUX tab is for a different type of packaging.

Setup project setup
HALCoGen version 04.07.00
IAR EWARM FS version 7.40.x
Chip: RM44L520PGE on custom hardware
Debugger: JLink Plus
Logic Analyzer: Saleae Logic Pro 16

Comparison project setup
HALCoGen version 04.07.00
IAR EWARM FS version 7.40.x
Chip: RM44L520PGE on XL2-RM46 Launchpad
Debugger: JLink Plus
Logic Analyzer: Saleae Logic Pro 16

Symptoms:
* The ECLK signal is all wrong. It looks like it's "trying" to output the expected frequency, but something's messing with it.
* Trying to use the vTaskDelayUntil() function in FreeRTOS, which should provide periodic behaviour, has too low periods and has a lot of jitter.
* When I close the IDE debugging session, the behaviour changes.
* If I run the same project with the same HALCoGen source code, create a task and start the scheduler but never invoke vTaskDelayUntil(), the ECLK signal is just fine.

Comparison: Running FreeRTOS on the XL2-RM46 shows none of these problems. ECLK is stable (shows up on my analyzer as flawless on 10 MHz, shows up with some jitter on 40 MHz)

Suspected cause:
* Some of the driver templates in the HALCoGen appears to have been copypasted from RM44L522ZWT_FREERTOS to RM44L520PGE_FREERTOS without making any corrections. For example the PINMUX tab is for the wrong type of packaging.

Other possible causes:
* Using IAR instead of CCS
* Flaws in our hardware.
* Some configuration difference between the two projects I haven't noticed
* Me.

Conclusion
There is probably something wrong with the configuration template for RM44L520PGE_FREERTOS

//Audun

over 7 years ago

0 Audun Knudsrod over 7 years ago

Intellectual 300 points

Update: The erratic timing issue stems from the IAR project configuration, not HALCoGen.
I keep forgetting that IAR has some default configuration parameters which causes the debugger the frequently halt/run the CPU.

The application now runs smoothly as far timing is concerned, but I am still pretty sure the configuration panes are wrong.

0 QJ Wang over 7 years ago in reply to Audun Knudsrod

TI__Guru**** 192486 points

Hello Audun,

Thanks for reporting the problem you saw in your HALCoGen generated code. But I don't see the freertos example project for L520PGE from HALCoGen. HalCoGen only provides freeRTOS example for L522ZWT:

The pimux panels for L520PGE and L522ZWT are different:

0 Audun Knudsrod over 7 years ago in reply to QJ Wang

Intellectual 300 points

I just did a fresh install of HALCoGen version 04.07.00 to check what I got, and it is still there (see first screenshot.).

For the project template called RM44L52PGE, I get the correct pinmux. For the one called RM44L520PGE_FREERTOS, I get the wrong pinmux (see second screenshot.).