Jeff Cooper wrote: > Does anyone have a BDI2000 configuration file for a DM355 EVM board > that they'd be willing to share? > > I assumed that it would be the same as a 644x config file, but the one > I've used successfully on the 644x boards only works on one of the two > DM355 EVM boards that I have. > > Board #1, the one that I can access, gives me when I attempt to get > JTAG access: > > - TARGET: waiting for target Vcc > - TARGET: processing power-up delay > - TARGET: processing reset request > - TARGET: BDI executes scan chain init string > - TARGET: Bypass check 0x00000001 => 0x00000002 > - TARGET: JTAG exists check passed > - Core#0: ID code is 0x07926001 > - TARGET: All ICEBreaker access checks passed > - TARGET: BDI removes RESET > - TARGET: BDI waits for RESET inactive > - TARGET: resetting target passed > - TARGET: processing target startup .... > - TARGET: processing target startup passed > > Board #2, the one I can't access, gives me: > > - TARGET: waiting for target Vcc > - TARGET: processing power-up delay > - TARGET: processing reset request > - TARGET: BDI executes scan chain init string > - TARGET: Bypass check 0x00000001 => 0x00000004 > - TARGET: JTAG exists check failed > - TARGET: Remove RESET and try again > - TARGET: BDI waits for RESET inactive > - TARGET: Bypass check 0x00000001 => 0x00000004 > - TARGET: JTAG exists check failed > # TARGET: resetting target failed > # JTAG: communication with target failed > - TARGET: target will be restarted in 10 sec > > Board #2 operates normally, it starts U-Boot and boots Linux, I just > can't get JTAG access to it. All of the jumpers and switches are set > the same on both boards. > > thanks, > Jeff >
We have our own hardware that shows this same behavior. One of our boards will work fine all the time, another will be random. The only solution for us is to power cycle the board - it never takes more than a couple of shots before it connects correctly. There are a couple of reasons why it may not work right in our environment - for one, we didn't wire up Jtag reset, and another we are using the DM350 (predecessor to the 355). Although I don't know of any reason why the package change from the 350 to 355 would be a problem Wish I had a better answer. Let me know if you find anything concrete! Steve Berry
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
