CCS/TMS320F28075: Previously Working Project now gets stuck in Boot ROM

Going a bit further...  Changed the 100K pull up to a 1K...  no dice...  still low (not quite zero) with roughly 3+ mA pulling it low.

At this point the only option was to override the defaults and actually write the OTP Boot Control Bits.

That worked, the processor now starts up to flash on reset and power off/on.  I still have no idea and it's not clear why GPIO72 is pulling low when the Boot ROM starts.

I added a check to the boot loader to verify the OTP is the correct bits, if not.  It writes it to values that force Flash.

#pragma CODE_SECTION(Flash_Setup_OTP,ramFuncSection);
Uint16 Flash_Setup_OTP(void)
{
	//Sets up OTP to force boot load from flash since we don't use TI's bootloader:

	Uint32 tempBoot;
	//Set the GPIO84 as boot select pin 1 (normally GPIO72 which is assigned to CANB):
	tempBoot = (Uint32)85 << 24;
	//Set the GPIO84 as boot select pin 0:
	tempBoot += (Uint32)85 << 16;
	//Set the Boot mode to Get/Wait (always boot to flash or wait if emulator attached):
	//0xFF is used as it defined the "other" which means FLASH/Wait, and means this value can be overwritten later:
	tempBoot += (Uint32)0xFF << 8;
	//Set the Key:
	tempBoot += (Uint32)0x5A;


	Uint16 Buffer[2];	  	//Data value Buffer
	Buffer[0] = (Uint16)(tempBoot & 0xFFFF);
	Buffer[1] = (Uint16)(tempBoot >> 16);

	volatile Uint32 Address = DCSM_Z2_BOOTCTRL_ADDRESS;

	//See if it's already written:
	if(DcsmZ2Otp.Z2OTP_BOOTCTRL != tempBoot)
	{
		//It's not:
		//Write the value:
		//DcsmZ1Otp.Z1OTP_BOOTCTRL = tempBoot;
		EALLOW;
		//Write the words to flash:
		volatile Fapi_StatusType oReturnCheck;
		oReturnCheck = Fapi_issueProgrammingCommand((uint32 *)Address, &Buffer[0], 2, 0, 0, Fapi_AutoEccGeneration);

		while(Fapi_checkFsmForReady() == Fapi_Status_FsmBusy);
		EDIS;

		if(oReturnCheck != Fapi_Status_Success)
		{
			//
			// Check Flash API documentation for possible errors
			//
			return FALSE;
		}

		return TRUE;
	}

	return TRUE;

}

NOTE:  This can be done to Z1 as well, but it works if you write either.  I figure I can still use Z1 if I want to change it something else later and I've already written Z2.

For someone looking to write these values, the process is semi complicated.  The writing of the values requires the CSM unlocked (done before this function), the flash API to be initialized (also done before this function), and then to write the values as if they are flash you are writing program code to (shown).  I don't think the ECC auto-generation option is needed for this section of flash, but it worked with it on, so I left it.