Hello Romain, The revision I am referring to is a hardware change, marked on the MSP432 silicon itself. It would also be great to know which version of MSP432Ware/DriverLib you are using. Enabling an interrupt without properly handling it inside of the startup_ msp432p401r _ccs.c interrupt vector table will definitely result in a defaultISR loop trap. Once again, since the cs_hfxt_start.c example works as expected then I would start with that example and slowly try to incorporate your own changes to see what causes the failure. Regards, Ryan
↧