Dont't knwo why but I can't reply in my own thread (https://community.infineon.com/t5/AIROC-Bluetooth/CYW20719-Core-Dump/m-p/394497#M2966) because it is some how locked.
Well, the answer is not the expected answer...I know how to use a core-dump using GDB or other tools. The initial question is that the 'core dump' (term wich is used in the topic https://community.infineon.com/t5/Resource-Library/CYW20719-and-CYW20735-Clocks-RTC-WatchDog-Timer-A...) is send using some Vendor HCI events (0x04 = HCI Event, 0xFF = Vendor Specific event, 0xF4 = event length)...This is NOT a 'common' core-dump as we all know. It's a Cypress/Infineon specific core dump generated by the ROM usinga function like dbfw_coredump_exception_cm3 or dbfw_coredump_exception_cm4.
I've been able to find the meaning of some events content by both looking at the 'headers' and also by exploring the internalblue tool code (https://github.com/seemoo-lab/internalblue) and build a tool which is almost complete. The only missing part is the CPU registers which I was able to dump because the addresses are common to me (the ARM Cortex-M series registers addresses).
I'd like to know if there's an official tool which would properly decode the received Cypress/Infineon specific core-dump send over the HCI uart, and would help us debugging what is happening.