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.
QUOTE(fladda @ Mar 9 2006, 04:37 PM)
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).