Thanks, that "hard fault" you indicated gave me hope, considering IAR totally crashes if I try to run my code but... that didn't solve the problem...
The equivalent of that line of code was already in the function __pe_initialize_hardware() ( in bsp_cm.c)
/* System clock initialization */
/* SIM_SCGC5: PORTE=1,PORTC=1,PORTA=1 */
SIM_SCGC5 |= (uint32_t)0x2A00UL; /* Enable clock gate for ports to enable pin routing */
As you can see, portA is enabled. My code used to be BEFORE that line, so, I moved my code to below all that, but no avail.
As I see it, the fact that IAR shows me bogus assembly even BEFORE I step through my new code should tell us something (but I don't know what).
In other words, simply compiling in some code that (potentially) talks to the port causes the assembly view to puke even though I've set a breakpoint before even actually running that code.
Does that makes sense?