The JTAG Programming interface is controlled by the same lock bits controlling all other programming interfaces. So it will be as secure as any of them.
On-Chip Debug
As Shown in the block diagram the only way to enabled OCD is to leave the lock bits off and then enabling both JTAGEN and OCDEN. In this state, the device is totally open anyway so the easiest way to steal code from it is to use any ISP programmer and dump out the code directly. With lock bits programmed, the OCD is disables ( regardless of LB mode ). So here the OCD is even more secure than the standard ISP interface where you can read out the memory contents in both LB mode 1 and 2.
Boundary Scan
This one is interesting, what if we could use the boundary scan chain to grab out info that we are not supposed to get hold of?! Luckily (unfortunately; depending who you are..), this is not possible. The Boundary Scan chain do not include any internal signal, only physical package pins. If the internal scan chain was accessible from the Boundary Scan interface, it would be possible to grab out the program counter and instruction word, thus stealing the contents of the flash
array bypassing the lock bits! Luckily (for most..) this is not possible. The internal scan chain is part of the OCD interface, and thus only accessible when no memory lock bits are programmed.
Conclusion
Our conclusion is that the JTAG interface is safe. But as with all security features they require that they are activated to have any effect
Keyword : tutorial ,prestige ,modern warfare ,youtube ,video games ,unsigned code ,unbanned ,modding ,xbox live ,xbox games ,torrent ,ratings ,patches ,modded xbox ,modded ,jtag programming ,jasper ,how to ,hard drive ,gamertag ,falcon ,external hdd ,download ,dashboard ,controller ,consoles ,console ,call of duty ,black ops

