Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - fladda

Pages: [1] 2
1
SIMpad forum / Can't Access The Bl Monitor Menu
« on: April 02, 2006, 03:51:58 pm »
I assume that you have been pressing the escape key on the serial terminal's keyboard - this should work.

Another way to get the menu to appear, is to reset your Simpad whilst at the same time holding down the lower Simpad front-panel key (the key that brings up the on-screen keypad in WinCE). Just successfully tested this with the 2.5.3 bootloader.

Ralph

2
SIMpad forum / No Serial Download Request
« on: March 25, 2006, 04:11:35 pm »
Thanks for that. Just tried this on my (broken) Simpad. Disabled the FiFo buffer on the serial port. Now the 2.5.3 boot-loader will load every time:-)

Before that it used to take 20-30 attempts, and only worked if the timing between pressing the reset on the Simpad and typing the serload command was perfect.

Ralph


Quote
Well...
I found the solution on the opensimpad.org forum:
I´m using Windows. I disabled the FIFO of the COM port in the device manager.

That did the trick. Unfortunately, the image that´s loaded is not very stable so I guess I´ll have to find somehting better...

Ronald
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120199\"][{POST_SNAPBACK}][/a][/div]

3
SIMpad forum / Can't Flash Simpad With Jtag
« on: March 17, 2006, 12:37:31 pm »
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

Quote
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]

4
SIMpad forum / Bost - Built-in Onboard Self Test
« on: March 16, 2006, 05:55:18 pm »
Tonight I managed to get the same corrupt bootloader message after re-loading the original Siemens 2.4 boot-loader with JTAG. So I'm pretty sure that the corrupt bootloader message is being caused by a corrupt flash EEPROM chip on this Simpad, and does not appear to be anything to do with the modified bootloader. That said, I would still recommend that only experienced JTAGers try the modified bootloader until it is proved to be 'safe'.

Since then I have successfully loaded my modified bootloader onto another Simpad, and this Simpad SL then successfully booted OK into WinCE 4.1 several times without incident.

I then went back and wrote the FabData string into this second Simpad using the BOST 'fs' (fabdata serial write) command. This was successful, but appeared to somehow corrupt the 4.1 WinCE image, as the next time the Simpad was reset I just got a continuous 'tartan reset' screen, with no sign of WinCE 4.1 appearing.

Ralph

5
SIMpad forum / Bost - Built-in Onboard Self Test
« on: March 15, 2006, 05:42:12 pm »
Well I reloaded the 4.1 WinCE image onto my Simpad using the modified 2.4 bootloader, and the bootloader is now shown as corrupt. However this Simpad has a fault somewhere so I'm not sure if this is anything to do with my modified bootloader or not !

After loading WinCE 4.1 image via serload I reset the Simpad and got:-

PBL V2.4 20.07.2001
Booting...
================================================
Siemens Switzerland Bootloader V2.4 20.07.2001
Running @206Mhz Processor ID 0x6901b118
Press ESC for monitor
Occupied Memory: [0x00004000-0x00008000],[0x00008014-0x0007cb9c]
Flash Id 0x00000018 at virt adr 0x05000000 Size 0x01000000
No 32Bit Flash detected 0x00000000
FlashImage Checksum 0x05040014-0x05061ab0=0x9dfa36c6 Bootloader Image OK
Fabdata Flash @0x05061ab4 Ram @0x00029ab4 FABDATA:
MSC2=0x211954e0 :: MQ200 - Revision ID=2 ...
Initialise PCMCIA Interface... done.
Codec UCB1200 ID:0x1005 Ver.5 Dev.0 Suppl.1 IO 0x00000000
No PCMCIA Card Attached
No serial download request
Boothdr at 0x05080000 -> 0x31415926
Loading executable with header 0x0000
[*********************/] 15209kB/sec
Done

<had very faint tartan screen (no backlight?) and nothing else, which is how this Simpad has been for weeks>

Then I reset the Simpad and got :-

PBL V2.4 20.07.2001
Booting...
================================================
Siemens Switzerland Bootloader V2.4 20.07.2001
Running @206Mhz Processor ID 0x6901b118
Press ESC for monitor
Occupied Memory: [0x00004000-0x00008000],[0x00008014-0x0007cb9c]
Flash Id 0x00000018 at virt adr 0x05000000 Size 0x01000000
No 32Bit Flash detected 0x00000000
FlashImage Checksum 0x05040014-0x05061ab0=0xc1a8fc2a BOOTLOADER DEFECT !
Fabdata Flash @0x05061ab4 Ram @0x00029ab4 FABDATA:
MSC2=0x211954e0 :: MQ200 - Revision ID=2 ...

<and nothing else>

Therefore, I strongly recommend that only those people with JTAG ports, cables and knowledge should attempt to load a modified boot-loader into their Simpads. At least until this has been tested a bit more.

Ralph

6
SIMpad forum / Bost - Built-in Onboard Self Test
« on: March 15, 2006, 03:40:31 pm »
>Is it really necessary to erase the bootstrap first? Can't you just load the modified >bootloader with serload?

I get a memory overlap error when I try serial loading things using the 2.4 bootloader. However this might be something wrong with the Simpad that I'm using, as I still haven't worked out why it won't work after flashing it with a WinCE 4.1 image (I suspect a damaged flash chip:-()

>As for entering BOST other than that... I'm sure there is a back door, like a string of >extended commands in a certain order or something like that. But on the other hand, >your method is easy enough not to worry about that anymore.

I did have quick look in the 2.4 bllotloader code for this. Could be there, but I couldn't find it. However I didn't look very hard or far...

>Do you think, with the new commands at our disposal now, there is an easy way to
>replace a PBL 1.4 with 2.4? I'm upgrading 16/32MB Simpads to 32/64, and this is >always a pain in the butt.

Sorry I have no experience of the older Simpads. Most of the BOST commands are for test purposes, and few if any actually modify the flash. Are you currently using JTAG for to get the bootloaders into the modified Simpads ?

Ralph

7
SIMpad forum / Bost - Built-in Onboard Self Test
« on: March 15, 2006, 02:43:02 pm »
WARNING - THIS MODIFICATION MIGHT 'BRICK' YOUR SIMPAD. UNTIL THIS HAS BEEN VERIFIED I WOULD STRONGLY RECOMMEND THAT LOADING A MODIFIED BOOTLOADER INTO YOUR SIMPAD SHOULD ONLY BE UNDERTAKEN BY PEOPLE WHO KNOW HOW TO USE JTAG TO RECOVER THE BOOT LOADER.

OK to get the BOST code to run from the Siemens monitor menu.

1. Find a copy of the original Siemens bootloader version 2.4  "loader_bl".

2. Change the byte at offset address:-

0x0016b4  from 0x71 ("q") to 0x62 ("b") (this is the important bit)

000016B4 CMPNE  R0,#&71 changes to CMPNE R0,#&62

3. Then change the string at offset 0x01d820 (in the text near the end of the file)

From Exit    ...    'q'     to     BOST   ...    'b'

This is just a cosmetic change to alter the menu string, as below:-

=====================
Monitor:
=====================
Boot from Flash   'f'
Boot from Net     'n'
Power Off         'o'
Erase PSM+Registry'p'
BOST              'b'
Erase Registry    'r'
Soft  Reset       's'
Print Fab-String  'w'

5. Save the modified bootloader file - I used the filename 'bootmod'.

6. Assuming that the Simpad already had the Siemens 2.4 or 2.5.3 bootloader installed. Connect up the serial cable to a terminal (I use Hyperterminal on a win98 PC) at 38.4kb 8N1 hardware handshaking.

7. Reset the Simpad and get the monitor menu. If monitor menu does not appear, then continuously press the 'escape' key on the PC keyboard whilst you reset the Simpad. Alternatively hold the lower key down on the Simpad whilst you press the reset key - this will bring up the monitor menu.

8. Enter the extended command 'x'.

9. Type 'e' and then 'b' which should being up the menu to erase the existing boot image. Type 'y' to erase. Note that this does not appear to erase the master boot file from the 16-bit part of the Simpad's flash. When you reset the Simpad, it will re-load the boot image.

=====================
Monitor:
=====================
Boot from Flash   'f'
Boot from Net     'n'
Power Off         'o'
Erase PSM+Registry'p'
Exit              'q'
Erase Registry    'r'
Soft  Reset       's'
Print Fab-String  'w'
-> x

Extended Command
Enter hexcode to execute:eb
Erasing Bootstrap. Please Wait
[***************************************-]

Bootstrap Erased.
You will see me never again.
ByeBye !

10. Rest the Simpad again. The following test should appear:-

PBL V2.4 20.07.2001
Booting internal PBL image...
================================================
Siemens Switzerland Bootloader V2.4 20.07.2001
Running @206Mhz Processor ID 0x6901b118
Press ESC for monitor
Occupied Memory: [0x00004000-0x00008000],[0x01f00014-0x01f74b9c]
Flash Id 0x00000018 at virt adr 0x05000000 Size 0x01000000
No 32Bit Flash detected 0x00000000
FlashImage Checksum 0x05040014-0x05061ab0=0xffff7959 Image Update, Old Image unchecked
Fabdata Flash @0x05040014 Ram @0x01f21ab4 Init Fabdata... Done
[***************************************\]
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart
Firmware Update Successfully Finished
Press Button to restart
etc.

11. Close the terminal session to release the serial port.

12. Use serial load programme to load in the modified bootloader.

C:\simpad> serload <filename>

13. When completed, reset the Simpad and you should now get the monitor option to enter BOST. Type 'h' for a list of the commands.

=====================
Monitor:
=====================
Boot from Flash   'f'
Boot from Net     'n'
Power Off         'o'
Erase PSM+Registry'p'
BOST              'b'
Erase Registry    'r'
Soft  Reset       's'
Print Fab-String  'w'
-> b

 Start BOST Siemens

BOST SIMPAD V1.01

etc...

e.g. memory monitor allows you to look as memory locations:-


z(b)yte,(w)ord,(l)ong :Adr: $00080000
 00080000 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080010 ff bf ff ff ff ff ff ff ff ff ff ff bf ff ff ff ................
 00080020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080050 ff ff ff ff ff ff ff ff ff ff ff ff fe ff ff ff ................
 00080060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080080 ff bf ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 00080090 ff ff ff ff ff ff ff ff fd ff ff ff df ff ff ff ................
 000800a0 fd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 000800b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 000800c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 000800d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
 000800e0 ff ff ff ff ff ff ff ff fe ff ff ff ff ff ff ff ................
 000800f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ef ff ff ................

Some of the commands appear to be vaguely useful, especially if you have a Simpad that has an unresolved problem (like one of mine:-().

A similar 'modification' will probably also work for the Siemens 2.5.3 bootloader, although I've not tried this yet. Note that I've found that the original Siemens rev. 2.4 bootloader to be easier to use for loading images, as the 2.4 bootloader never has a problem 'seeing' the incoming serial data. I often have to do 20-30 resets in succession with the 2.5.3 loader before it 'sees' that there is a serload 'in progress'. I suspect that this has caused many people to believe that their Simpad is 'bricked' !

And for all I know you can enter BOST directly without modifying the bootloader. If anybody knows how to do this, then please do let us know...

Hope that somebody out there finds this useful...

Ralph

8
SIMpad forum / Bost - Built-in Onboard Self Test
« on: March 15, 2006, 01:55:02 pm »
I also found the BOST stuff whilst I was having a look at the bootloader code using my old Acorn RiscPC (which comes complete with a built in ARM dissassembler;-)

I had a very lucky guess that the BOST code was disabled by Siemens by removing the 'b' option in the Monitor menu. I just changed one of the other letters in the menu assembler code to a 'b'.

=====================
Monitor:
=====================
Boot from Flash   'f'
Boot from Net     'n'
Power Off         'o'
Erase PSM+Registry'p'
Exit              'q'
Erase Registry    'r'
Soft  Reset       's'
Print Fab-String  'w'
->

Would make sense to change the 'q' to a 'b'. Then exiting from the monitor menu would take you straight into the BOST routines.

I will re-modify the code just to be sure, and then post the instructions how to modify the Siemens bootloader...

Ralph

Quote
These items look very familiar!!! I saw most of them looking at the bootloaders with a hex-editor, and thats what made me post the question with the extended commands. Veeery interesting!

Digi

[div align=\"right\"][a href=\"index.php?act=findpost&pid=118730\"][{POST_SNAPBACK}][/a][/div]

9
SIMpad forum / Bost - Built-in Onboard Self Test
« on: March 15, 2006, 09:07:45 am »
The original Siemens bootlader contains the code for BOST - the Simpad's Built-in Onboard Self Test routines. BOST even has an option to programme the fabdata string(s) - in answer to Digi's question this is how it can be done !

Not sure if you can access BOST using the standard Siemens 2.4 or 2.5.3 bootloaders. I managed to get BOST running by simply changing one byte of the 2.4 bootloader code, and then reflashing the modified 2.4 bootloader into my Simpad.

Instructions to follow (first I want to have a look at the test commands:-)

Ralph

BOST Commands:
a,A b,B  : Connect Audio Path Mike => Speaker and Headset, exit with 'e'
a,A h,H or s,S : Audio Path Mike => Headset or Speaker, exit with 'e'
a,A t,T  : Short Tone burst to Speaker and Headset
b,B 1..6 : Control Backlight brightness
c,C i,I  : Init and Accesstest CODEC UCB1200 / UCB1300
c,C j,J 1..3 : Get CODEC AD1: BL_POWER, AD2: DC_IN_FUSED, AD3: ICHARGE
c,C k,K  : Get P and X,Y-Coordinates from Touch Panel
c,C l,L  : Loop Get P and X,Y-Coordinates, exit with 'e'
d,D a,A  : ATM commands to DECT Modul MD34
d,D b,B  : Set DIV_BAUD for UART1 (default = 0x01)
d,D c,C  : Connect MD34 to DECT Base Station BS3070
d,D d,D or i,I : DECT Module Power Down or Init DECT Modul MD34
d,D e,E  : Escape Command +++ to DECT Modul
d,D f,F  : Back to Factory settings DECT Modul
f,F d,D or r,R : Display Fabdata Magic or Read Fabdata buffer
f,F s,S  : Write Serial number to Fabdata buffer
f,F t,T or l,L : Write Test Date Ttt.mm.jj or Load Date Ltt.mm.jj
g,G b,B or w,W : Fill Background with Black or White
g,G h,H or v,V : Fill Color Pattern horizontal or vertical
g,G l,L or n,N : Write White or Black Lines
h,H,?    : Help text
i,I b,B  : Set DIV_BAUD for UART2 (default = 0x01)
i,I r,R or t,T : Receive or Transmit 20 Bytes from/to IrDA
l,L 2 or 0 : Set LED2 on or off
m,M a,A  : Set ACCESS to RAM (default = 0x32)
m,M b,B or e,E : Set RAM BEGIN-ADR or END-ADR (default = 0)
m,M d,D or m,M : RAM Data Test or RAM Memory Test
n,N c,C or g,G or s,S : Get CODEC or GPIO or CS3 DIN Port
n,N k,K or m,M : Alternate Output 32kHz or 3.6MHz at GPIO_27
o,O h,H or l,L : High or Low to CS3 Latch Pins
o,O i,I or o,O : In or Out in GPIO Pin Direction Register (GPDR)
o,O c,C or s,S : Clear or Set GPIO Output Register (GPCR or GPSR)
p,P 0 or 3 or 5 : PCMCIA Vcc/Vpp to 0V or 3.3V or 5V
p,P a,A or s,S : Set ACCESS Variable or DOUT Variable
p,P d,D or m,M : PCMCIA RAM Data Test or PCMCIA Memory Test
p,P r,R or w,W : Read DIN from or write DOUT to PCMCIA Address
r,R      : Soft Reset
s,S a,A or s,S or i,I : Smart Card Answer to Reset (ATR) or Init TDA8007
u,U d,D or e,E : Disable or Enable USB Device Controller
u,U s,S  : Get UDC Status Register
v,V      : BOST Version
x,X      : Power Off
y,Y      : FLASH Burst Test
z,Z      : Memory Dump
(Textlen 2297 Bytes)

10
SIMpad forum / Siemens Bootloader Extended Commands
« on: March 13, 2006, 06:33:42 am »
Just to correct my own post - I was wrong. The 'x e0' and 'x e1' commands appear to work the same on rev. 2.4 and 2.5.3 Siemens bootloaders.

e0 erases the flash from 05080000 to 06000000 (16Mbytes minus the boot loader)
e1 erases the flash from 08000000 to 09000000 (16Mbytes)

Assuming that these Siemens EEPROM addresses are correct, then the 'y' erase flash option in the 2.5.3 bootloader appears to show the wrong addresses for erasing ??
'y' reports to erase the flash ROM between 05080000 to 07000000

I think that this should be 05080000-06000000, 08000000-09000000 using the Siemens memory map ??

Note that the 'y' erase flash option is not available in the original 2.4 Siemens bootloader. However it does appear that the extended commands 'x e0' and 'x e1' commands perform the same function to erase the flash, and can be used in both the 2.4 and the 2.5.3 Siemens bootloaders.

The 'x eb' extended command provides an extremely useful method of going back from the Siemens 2.5.3 bootloader to the original 2.4 bootloader.

So we can erase all of the flash in the Simpad using the E0/E1 commands, except for a small area at the start of the second EEPROM chip (4 flash erase blocks or 512kbytes) corresponding to the area occupied by the bootloader in the first EEPROM chip.

Ralph

Quote
Incidentally the 'x' commands E0 and E1 appear to work differently with the original Siemens 2.4 bootloader, to the modified (linux/WinCE) 2.5.3 bootloader. Using the E0 and E1 commands allows you to delete different areas of the flash from the 2.4 bootlader (similar to the 'y' command with the 2.5.3 bootloader).

[div align=\"right\"][a href=\"index.php?act=findpost&pid=117769\"][{POST_SNAPBACK}][/a][/div]

11
SIMpad forum / Erase Flash Chip Before Jtaging
« on: March 12, 2006, 03:02:03 pm »
JTAG flash programming is *painfully* slow. I reckon that flashing a 16Mbyte file using JTAG on the Simpad at the 'normal speed would take about 24 hours (or more?). My method achieves almost the same result, but uses the 'erase block' function to clear the flash more quickly. That said flashing the contents of the flash to 0x00000000 would always be better than erasing the flash blocks (to 0xFFFFFFFFFF ???? or whatever ?), as 0x00000000 corresponds to the ARM instruction :-

ANDEQ   R0,R0,R0 ; this is effectively the same as a NOP instruction.

So if this 'code' was ever run in error, it would not do anything 'dangerous', but eventually I guess that an ARM memory exception would occur ??

Ralph


Quote
Why don't you create a file with 16 Mbytes of 0x00 and flashmem it in one step?

I suppose flashmem 0 16mbfile erases the first bank, while flashmem 0x1000000 16mbfile erases the second bank. Haven't tried it, though...

Digi

Quote
There are times when even re-loading the Siemens 2.4 SL bootloader with the JTAG utility does not appear to recover a 'bricked' Simpad. For example loading the Siemens 2.4 CL bootloader into a Simpad SL appears to be a good way of 'bricking' your Simpad ! (I tried this just to see what happens).

I found that JTAG (version 2.4) supports a scripting option. So I created a file called 'null' with the contents of just 4 bytes (0x00 0x00 0x00 0x00). Then used the following script file to write this data into every block of the first 16-bit flash chip. During the flash process, all EEprom flash blocks are first erased, so the script below effectively erases the 16-bit 'accessible' flash chip that is used to hold the boot-loader.


[div align=\"right\"][a href=\"index.php?act=findpost&pid=118166\"][{POST_SNAPBACK}][/a][/div]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=118173\"][{POST_SNAPBACK}][/a][/div]

12
SIMpad forum / Erase Flash Chip Before Jtaging
« on: March 12, 2006, 09:12:21 am »
There are times when even re-loading the Siemens 2.4 SL bootloader with the JTAG utility does not appear to recover a 'bricked' Simpad. For example loading the Siemens 2.4 CL bootloader into a Simpad SL appears to be a good way of 'bricking' your Simpad ! (I tried this just to see what happens).

I found that JTAG (version 2.4) supports a scripting option. So I created a file called 'null' with the contents of just 4 bytes (0x00 0x00 0x00 0x00). Then used the following script file to write this data into every block of the first 16-bit flash chip. During the flash process, all EEprom flash blocks are first erased, so the script below effectively erases the 16-bit 'accessible' flash chip that is used to hold the boot-loader.

Command is :-

jtag> script
Q. Does anybody know a good way of completely erasing the 2nd flash ROM chip in the Simpad ?

My experience is that the contents of certain locations in the flash chips can cause all sorts of different failure modes when going from WinCE-Linux, or back from Linux->WinCE.

Ralph

**********************
flashmem 0x00000000 null
flashmem 0x00020000 null
flashmem 0x00040000 null
flashmem 0x00060000 null
flashmem 0x00080000 null
flashmem 0x000a0000 null
flashmem 0x000c0000 null
flashmem 0x000e0000 null
flashmem 0x00100000 null
flashmem 0x00120000 null
flashmem 0x00140000 null
flashmem 0x00160000 null
flashmem 0x00180000 null
flashmem 0x001a0000 null
flashmem 0x001c0000 null
flashmem 0x001e0000 null
flashmem 0x00200000 null
flashmem 0x00220000 null
flashmem 0x00240000 null
flashmem 0x00260000 null
flashmem 0x00280000 null
flashmem 0x002a0000 null
flashmem 0x002c0000 null
flashmem 0x002e0000 null
flashmem 0x00300000 null
flashmem 0x00320000 null
flashmem 0x00340000 null
flashmem 0x00360000 null
flashmem 0x00380000 null
flashmem 0x003a0000 null
flashmem 0x003c0000 null
flashmem 0x003e0000 null
flashmem 0x00400000 null
flashmem 0x00420000 null
flashmem 0x00440000 null
flashmem 0x00460000 null
flashmem 0x00480000 null
flashmem 0x004a0000 null
flashmem 0x004c0000 null
flashmem 0x004e0000 null
flashmem 0x00500000 null
flashmem 0x00520000 null
flashmem 0x00540000 null
flashmem 0x00560000 null
flashmem 0x00580000 null
flashmem 0x005a0000 null
flashmem 0x005c0000 null
flashmem 0x005e0000 null
flashmem 0x00600000 null
flashmem 0x00620000 null
flashmem 0x00640000 null
flashmem 0x00660000 null
flashmem 0x00680000 null
flashmem 0x006a0000 null
flashmem 0x006c0000 null
flashmem 0x006e0000 null
flashmem 0x00700000 null
flashmem 0x00720000 null
flashmem 0x00740000 null
flashmem 0x00760000 null
flashmem 0x00780000 null
flashmem 0x007a0000 null
flashmem 0x007c0000 null
flashmem 0x007e0000 null
flashmem 0x00800000 null
flashmem 0x00820000 null
flashmem 0x00840000 null
flashmem 0x00860000 null
flashmem 0x00880000 null
flashmem 0x008a0000 null
flashmem 0x008c0000 null
flashmem 0x008e0000 null
flashmem 0x00900000 null
flashmem 0x00920000 null
flashmem 0x00940000 null
flashmem 0x00960000 null
flashmem 0x00980000 null
flashmem 0x009a0000 null
flashmem 0x009c0000 null
flashmem 0x009e0000 null
flashmem 0x00a00000 null
flashmem 0x00a20000 null
flashmem 0x00a40000 null
flashmem 0x00a60000 null
flashmem 0x00a80000 null
flashmem 0x00aa0000 null
flashmem 0x00ac0000 null
flashmem 0x00ae0000 null
flashmem 0x00b00000 null
flashmem 0x00b20000 null
flashmem 0x00b40000 null
flashmem 0x00b60000 null
flashmem 0x00b80000 null
flashmem 0x00ba0000 null
flashmem 0x00bc0000 null
flashmem 0x00be0000 null
flashmem 0x00c00000 null
flashmem 0x00c20000 null
flashmem 0x00c40000 null
flashmem 0x00c60000 null
flashmem 0x00c80000 null
flashmem 0x00ca0000 null
flashmem 0x00cc0000 null
flashmem 0x00ce0000 null
flashmem 0x00d00000 null
flashmem 0x00d20000 null
flashmem 0x00d40000 null
flashmem 0x00d60000 null
flashmem 0x00d80000 null
flashmem 0x00da0000 null
flashmem 0x00dc0000 null
flashmem 0x00de0000 null
flashmem 0x00e00000 null
flashmem 0x00e20000 null
flashmem 0x00e40000 null
flashmem 0x00e60000 null
flashmem 0x00e80000 null
flashmem 0x00ea0000 null
flashmem 0x00ec0000 null
flashmem 0x00ee0000 null
flashmem 0x00e00000 null
flashmem 0x00f20000 null
flashmem 0x00f40000 null
flashmem 0x00f60000 null
flashmem 0x00f80000 null
flashmem 0x00fa0000 null
flashmem 0x00fc0000 null
flashmem 0x00fe0000 null
flashmem 0 simpadSL.rom
**********************

13
SIMpad forum / Can't Flash Simpad With Jtag
« on: March 11, 2006, 08:59:25 am »
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

Quote
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]

14
SIMpad forum / No Serial Download Request
« on: March 11, 2006, 08:53:07 am »
Keep trying, and hit the Simpad's reset key at different times relative to typing the serload request. Eventually the flash image will start to load (as long as you don't then get the memory 'overlap' message). Often takes 10-20 attempts to get the flash load started.

Start with hitting the reset on the Simpad about 0.1 seconds before hitting <enter> for the serload request. Each subsequent attempt hit the Simpad reset about 0.05 seconds later each time... Keep trying.

However, even when I manage to load the flash image onto one my Simpads, the screen says flash completed OK etc. but the Simpad just keeps displaying the 'tartan' screen forever:-( WinCE 4.1 never seems to start up. I tried Wince 3.0 and 4.0 and these are just the same. I am wondering if there is some area of the 2nd flash IC that needs to be cleared (I completely erased the first flash IC using JTAG). I cleared everything I could find first using the 2.5.3 bootlader options 'r', 'y' and 'p', and the extended options e0 and e1.

Ralph


Quote
Quote
ronaldw,

type the serload command and then hit ENTER and reset the Simpad at the same time, not ENTER first and then reset. Sometimes helps.

Digi
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116986\"][{POST_SNAPBACK}][/a][/div]
Thanks, I will try it. I'm afraid I bricked my simpad, but I guess there's still hope...

Ronald
[div align=\"right\"][a href=\"index.php?act=findpost&pid=117188\"][{POST_SNAPBACK}][/a][/div]

15
SIMpad forum / Siemens Bootloader Extended Commands
« on: March 09, 2006, 10:37:52 am »
No I've not found a way of getting the FabData reloaded yet. However I guess that you might be able to use the flashmem JTAG command to put the correct string back into the flash ?? However JTAG can only access the first flash IC, presumably in 16-bit mode. I guess that the FabData string is probably 32-bit aligned ?? (I'm just guessing here as I am not sure how the memory map of the Simpad's flash looks in detail).

Perhaps loading WinCE3.0 initialises the FabData string ?? (I'll try and see what happens). Siemens must had dome this somehow ?

Is getting the FabData string re-entered important ?

Incidentally the 'x' commands E0 and E1 appear to work differently with the original Siemens 2.4 bootloader, to the modified (linux/WinCE) 2.5.3 bootloader. Using the E0 and E1 commands allows you to delete different areas of the flash from the 2.4 bootlader (similar to the 'y' command with the 2.5.3 bootloader).

When I get my Simpad working with WinCE 4.1 (I've been working on this for almost 2 weeks now!), I will write up all of my experiences, and suggestions. I've had about 20 different lock up states all with different symptoms. Usually these lock-ups stop the bootladers from working correctly. However all these states appear to be caused by different things in the flash. Erasing all 128 blocks in the first flash chip using a JTAG script, and then re-loading the 2.4 bootloader using the JTAG command "flashmem 0 simpadSL.rom" appears to always allow the 2.4 boot-loaders to be loaded with serload, and then the primary 2.5.3 bootloader to be loaded OK. Don't think that I've ever managed to load the alternative 2.5.3 bootloader though ??

Ralph

Quote
Do you know of a way to put the FabData back in once it has been deleted?

Digi
[div align=\"right\"][a href=\"index.php?act=findpost&pid=117597\"][{POST_SNAPBACK}][/a][/div]

Pages: [1] 2