1
Show Posts
This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.
Messages - cavokz
2
Bus Blaster JTAG debugger / Re: Resurrecting my BB v2.5
Select device:
Device 0 (Serial Number: A
Device 1 (Serial Number: B
======================================================
SUCCESS (Connected to the FTDI.A)
SUCCESS (reset)
SUCCESS (usb parameters set)
SUCCESS (event chars disabled)
SUCCESS (timeouts set)
SUCCESS (latency set)
SUCCESS (flow control disabled)
SUCCESS (MSSPE reset)
SUCCESS (MPSSE on)
START TESTING
======================================================
00000001 11111111
00000010 11111111
00000100 11111111
00001000 11111111
00010000 11111111
00100000 11111111
01000000 11111111
10000000 11111111
00000000 11111111
10101010 11111111
01010101 11111111
00000000 11111111
11111111 11111111
Testing complete, errors: 12
At the bottom of the linked page I read "We highly recommend users upgrade to a non-selftest buffer immediately". Need to understand whether I need to program any special buffer for this test or not.
3
Bus Blaster JTAG debugger / Resurrecting my BB v2.5
I'd like to resurrect my BB v2.5 but urJtag returns a "TDO seems stuck to 0". I get this error with two different target boards which otherwise seem to work fine when connected to a Segger J-Link.
I'm not sure what I exactly did with my BB before burying it in a box so I followed the instructions at http://dangerousprototypes.com/docs/Bus_Blaster_v2_%26_v3_buffer_logic and successfully reprogrammed the buffer with BBv2-JTAGkey-v1.3.svf.
I'm using a hand built urJtag from git and I'm leaving the JP4 open, so powering the buffer with the target 3.3V which I verified arrives to the BB's jtag connector.
How I can move on?
Thanks,
Dom