For some time now we have had problems with JTAGing loon-3's using bflash.
About 50% of the time it fails with a seg fault.
I've spent some time looking at it this morning and found that the seg fault
is caused by it trying to continue with the programming after it fails to
read the CFI data. I've now fixed the error handling.
This leaves us with the real problem.
The bflash output looks like:
colin@buzet:~/balloon-bin$ sudo bflash balloon3 -f -n bootldrpxa.small
jtagSetDeviceAttributes
Testing port address 3bc ... not found.
Testing port address 378 ... found.
Setting LPT port to 0x378
id = 0x79265013
Expected part found Part ID = 0x5013, Manufacturer = 0x13, Revision = 0x7
No CFI Data Obtained
0 : 0x63 0x6c 0x0 0x3 0x0 0x0 0xc 0x3 0x2f 0x0 0x4c 0x4f 0x8 0x3 0xac 0x8f
16 : 0xff 0x8d 0xe 0xa0 0x2d 0x0 0xac 0x9f 0xfc 0x9f 0x86 0x0 0xc 0xa0 0xf0 0x9f
32 : 0x91 0x0 0x10 0x16 0xe4 0x9f 0x8e 0x0 0xc 0xa0 0xff 0x9d 0xfe 0xff 0x6c
0x8f
48 : 0xff 0x8d 0xe 0xa0 0x1d 0x0 0x70 0x9f 0xbc 0x9f 0x76 0x0 0xc 0xa0 0xb0 0x9f
FATAL: Failed to read CFI Data. Can't find NOR.
Looking at the query_cfi routine it expects the first three bytes to be "QRY".
Anyone got any ideas about what might be causing this?
regards,
Colin
--
Colin Tuckley | colin@tuckley.org | PGP/GnuPG Key Id
+44(0)1903 236872 | +44(0)7799 143369 | 0x1B3045CE
"Apple" (c) Copyright 1767, Sir Isaac Newton.
(text/plain)