s32k344 hse use lauterbach

[YanyiQiu]

hi

i have been ran "HSE_DEMOAPP_S32K3XX_0_2_1_0" demo successfully in s32k344 development board(XS32K3XXEVB-Q257) , use lauterbach emulator / trace 32 .

and it can debug another non-HSE software project in this s32k344 development board (installed the Hse firmware), use PE/USB MULTILINK  in  S32DS when enable "nxp_s32k342_1x32x456k_hse_enabled.arp" .

but it can't download the non-HSE software  project and can't debug the non-HSE software  project in the development board, use lauterbach emulator / trace 32.(default s32k3.cmm in trace32 installation directory)

is there any script in lauterbach emulator / trace 32 like the "nxp_s32k342_1x32x456k_hse_enabled.arp" in PE/USB MULTILINK ?

thanks a lot

[tanga_pivotal]

Hi, 

I have only S32K3_HSE_DEMOExamples_1_0_0.  Can someone point me where I can download the HSE_DEMOAPP_S32K3XX_0_2_1_0? 

Thanks

[lukaszadrapa]

Hi @YanyiQiu 

I can see that default script (c:\T32\demo\arm\flash\s32k3.cmm) already sets area 0x7D_4000 - 0x7F_FFFF as NOP, so it should work for FULL_MEM firmware.

If you use AB SWAP, it's just necessary to configure reserved area in active block as NOP at 0x5D_4000 - 0x5F_FFFF. Just add this to the default script:

FLASH.ChangeType 0x005D4000--0x005FFFFF NOP

Regards,

Lukas

[YanyiQiu]

Thank you for your attention .

the demo use FULL_MEM firmware .

I tried it again like you said , use the default script (c:\T32\demo\arm\flash\s32k3.cmm) already sets area 0x7D_4000 - 0x7F_FFFF as NOP in s32k344 development board ( installed the Hse firmware). the software project is a non-HSE software project as mentioned earlier.

when download the app, it has a "checking flash" message, then trigger a error "FLASH programming error around address c:0x10000000" in lauterbach emulator / trace 32.

then i add the statements to this script like below.

        FLASH.ChangeType 0x1B000000--0x1B001FFF NOP
        FLASH.ChangeType 0x10000000--0x10000100 NOP
        FLASH.ChangeType 0x10017FFF--0x1001FFFF NOP

the app can be downloaded into the mcu successfully . meanwhile ,it can be running online in trace32.

but when i RESetOut in the trace32, it can't finished the job normally(reset the mcu). when i "run/go" in trace32, it will trigger a "Hardfault_handler".  somtimes , it stop in "sys_m7_cache_init()" .  power off and resart the s32k344 development board, then "attach" in trace32, it can be running again.

but i debug the same non-HSE software project as mentioned earlier use a PE/USB MULTILINK, it can be downloaded normally, and it can be debug normally include "reset / run" in s32ds.

As described above, is there a problem with the script of lauterbach/trace32 ?

[lukaszadrapa]

I would check it like this:

- load the project by pemicro and test if it works also after power-on.

- attach lauterbach debugger. Dump the flash memory to a file.

- now erase the flash and load the same elf or srec file to the flash by the script in lauterbach.

- dump the flash again.

- compare the files. Is it the same? If no, where's the difference? Which block?