NXP MBDT runs perfectly on MPC5744P and runs motor using MotorGD board until....
... I expand the application code such that the Flash segment runs beyond 0xFFFFH (i.e. from 0x01000000 to above 0x01010000).... and at that point it fails to come out of reset to start application. Reduce it below the magic 0x1010000H(such that .appKey resides in the first 64K) and it all works... highly repeatable.. and doesn't care which code I include/exclude to get the effect.
The MOT file appears correct, and includes all the Bootloader requirements of RCHW, address of application start, timeout value, address of appkey.... all pointing to the correct addresses and the appkey is clearly present at the right address in the .Mot S-records.
I can't see any 'memory size' model style restrictions in the build (running the automatic S32DS and RAppID elements, or standalone build and programming tools).. also tried changing the Default Target Memory Definition in Matlab - same result (works OK when smaller than 64K flash, not when above). RAppID reports correct size (from S-records) in each case.
Have I missed something that needs to be set to allow me to 'grow' the code size? (I have lots more to implement - but don't expect final size to be >128K of Flash).
App RAM usage is trivial at >16K (at Location 0x40000000 up) . Stacks and Heap etc are at 0x50800000 and are unchanged .. approx allocated 0x1000 each)
Success Example (same build some content commented out before recompiling)