1/1 
|
JTAG self-test information
by dabing on Dec 9, 2013 |
dabing
Posts: 8 Joined: Apr 25, 2011 Last seen: May 22, 2014 |
||
|
The fail information is follows. I wonder how it means. Can anyone help me ?
openrisc@openrisc-VirtualBox:~$ adv_jtag_bridge -t ft245 'usb_blaster' interface using libftdi current latency timer: 2 Enumerating JTAG chain... Devices on JTAG chain: Index Name ID Code IR Length ---------------------------------------------------------------- 0: OC_TAP 0x149511C3 4 Target device 0, JTAG ID = 0x149511c3 IDCODE sanity test passed, chain OK! *** Doing self-test *** Stall or1k - CPU(s) stalled. SRAM test: expected 11112222, read 11112222 expected 33334444, read 33334444 expected 55556666, read 55556666 expected 77778888, read 77778888 expected 9999aaaa, read 9999aaaa expected bbbbcccc, read bbbbcccc expected ddddeeee, read ddddeeee expected ffff0000, read ffff0000 expected dedababa, read dedababa SRAM test passed Testing CPU0 (or1k) - writing instructions Setting up CPU0 Starting CPU0! Read npc = 00000010 ppc = 00000028 r1 = 00000005 Expected npc = 00000010 ppc = 00000028 r1 = 00000005 Read npc = 00000028 ppc = 00000028 r1 = 00000008 Expected npc = 00000010 ppc = 00000028 r1 = 00000008 Read npc = 00000024 ppc = 00000020 r1 = 0000000b Expected npc = 00000028 ppc = 00000024 r1 = 0000000b Read npc = 00000020 ppc = 0000001c r1 = 00000018 Expected npc = 00000024 ppc = 00000020 r1 = 00000018 Read npc = 0000001c ppc = 00000018 r1 = 00000031 Expected npc = 00000020 ppc = 0000001c r1 = 00000031 Read npc = 00000020 ppc = 0000001c r1 = 00000032 Expected npc = 00000024 ppc = 00000020 r1 = 00000032 Read npc = 00000010 ppc = 00000028 r1 = 00000063 Expected npc = 00000014 ppc = 00000010 r1 = 00000063 Read npc = 00000024 ppc = 00000020 r1 = 00000065 Expected npc = 00000028 ppc = 00000024 r1 = 00000065 Read npc = 00000010 ppc = 00000028 r1 = 000000c9 Expected npc = 00000010 ppc = 00000028 r1 = 000000c9 result = deaddeb1 Self-test FAILED *** Bailing out! |
|||
1/1