Can't Flash Simpad With Jtag

[spacko]

Hi there!

After hours of trying to reflash the rom of my simpad (including lots of soldering and cable building, according to the brilliant  howto from opensimpad.org) i'm stuck.

jtag recognizes the cable and identifies the cpu correctly (SA1110).
But detectflash does not seem to identify the flash memory.

Here is the output of jtag:

Code: [Select]

jtag> cable parallel 0x378 DLC5
Initializing Xilinx DLC5 JTAG Parallel Cable III on parallel port at 0x378
jtag> detect
Device Id: 10001001001001100001000000010011
  Manufacturer: Intel
  Part:         SA1110
  Stepping:     B4
  Filename:     /usr/local/share/jtag/intel/sa1110/sa1110
jtag> detectflash
ROM_SEL: 16 bits
Flash not found!

Does this mean my simpad is finally and completely dead? Or is there still hope?

btw, I'm on Debian Linux, but the error was reproducable on Gentoo Linux and Cygwin under Windows XP.

[fladda]

I sometimes get the same message with my Simpad. However the 'detectflash' command works correctly about 95% of the time for me.

How long is your JTAG cable ? If its more than 20cm I would first try again with a shorter cable.

I found that building the JTAG cable was the easy bit, compared to getting JTAG compiled under Mandriva. However compiling JTAG was easy compared to actually getting the flash IC in a fit state again, after 'accidentally' loading the CL boot image into a Simpad SL.

Ralph

Hi there!

After hours of trying to reflash the rom of my simpad (including lots of soldering and cable building, according to the brilliant  howto from opensimpad.org) i'm stuck.

jtag recognizes the cable and identifies the cpu correctly (SA1110).
But detectflash does not seem to identify the flash memory.

Here is the output of jtag:

Code: [Select]

jtag> cable parallel 0x378 DLC5
Initializing Xilinx DLC5 JTAG Parallel Cable III on parallel port at 0x378
jtag> detect
Device Id: 10001001001001100001000000010011
  Manufacturer: Intel
  Part:         SA1110
  Stepping:     B4
  Filename:     /usr/local/share/jtag/intel/sa1110/sa1110
jtag> detectflash
ROM_SEL: 16 bits
Flash not found!

Does this mean my simpad is finally and completely dead? Or is there still hope?

btw, I'm on Debian Linux, but the error was reproducable on Gentoo Linux and Cygwin under Windows XP.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=114830\"][{POST_SNAPBACK}][/a][/div]

[fladda]

Just had your exact symptoms where JTAG was unable to 'see' the flash chip. Problem was caused by not erasing the product code from the flash first. Guess that the StrongARM processor and the JTAG were both accessing the flash at the same time ??

To erase the Simpad's product firmware :-

Remove mains connector. Power down Simpad by pressing the micro-switch next to JTAG connector, and carefully remove the JTAG cable. Connect up the serial cable and use a terminal running at 115kbaud 8N1 hardware handshaking.

With the Siemens 2.5.3 bootloader in monitor mode, select the 'y' option to erase the flash.

With the Siemens 2.4 bootloader in monitor mode, use the extended commands to erase flash banks 0 and 1. Note that these commands also work with the 2.5.3 bootloader.

>'x' then 'e0' then answer yes
>'x' then 'e1' then answer yes

Hope this is helpful,

Ralph

Hi there!

After hours of trying to reflash the rom of my simpad (including lots of soldering and cable building, according to the brilliant  howto from opensimpad.org) i'm stuck.

jtag recognizes the cable and identifies the cpu correctly (SA1110).
But detectflash does not seem to identify the flash memory.

Here is the output of jtag:

Code: [Select]

jtag> cable parallel 0x378 DLC5
Initializing Xilinx DLC5 JTAG Parallel Cable III on parallel port at 0x378
jtag> detect
Device Id: 10001001001001100001000000010011
  Manufacturer: Intel
  Part:         SA1110
  Stepping:     B4
  Filename:     /usr/local/share/jtag/intel/sa1110/sa1110
jtag> detectflash
ROM_SEL: 16 bits
Flash not found!

Does this mean my simpad is finally and completely dead? Or is there still hope?

btw, I'm on Debian Linux, but the error was reproducable on Gentoo Linux and Cygwin under Windows XP.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=114830\"][{POST_SNAPBACK}][/a][/div]