I am in the process of writing a debug monitor for the OMAP3530 and when I dump the AUTHSTATUS register at address 0x54011fb8 I get back a value of 0xAE which from what I read in section 12.5.10 of the Cortex-A8 TRM would appear to indicate that NIDEN is set to enable non-invasive debugging but DBGEN isn't set. This appears to be stopping me from setting the Monitor mode bit (bit 15) in the Debug Status and Control Register. The only mention I seem to find in the OMAP3530 TRM about the DBGEN signal is almost at the end of the document in section "25.6.4 Debugger Address Space". In the last sentence of this section it says the following, "The DBGEM signal on the Cortex-A8 is driven by setting bit 13 at address 0xD401 D030 in the DAP-APB address space." I think it means DBGEN and not DBGEM since I can't find a DBGEM signal listed in the Cortex-A8 manual. I am not that familiar with the APB but I don't think that the address 0xD401D030 is the actual address where the DAP is visible from the Cortex-A8 itself but from external debugger JTAG hardware. There is a dump of the OMAP3530 ROMTable taken from OpenOCD at http://elinux.org/BeagleBoardOpenOCD#ROMTable and it shows a 0xd401d003 entry that point to a component base address of 0x5401d00 so think that the register mentioned in the OMAP3530 TRM should actually be 0x5401d030 from the CPU but all of my write accesses to this register appear to be ignored and have no effect. I am able to modify some bits at memory location 0x5401D010 so I don't think that this whole module is off limits to the CPU. Hopefully I am just doing something stupid that someone will point out to me and get me over this hurdle. Thanks for the help, Stanley