Re: [E3-hacking] Understanding the E3s Partitions

>You'd need to look into what pbltool is seeking and not finding. >But as long as you're still getting PBL printing out its banner, it's >there and willing to alter the main flash memory for you. I don’t know what I need to do next and how to find out what pbltool is looking for..? I don’t know

Re: [E3-hacking] Understanding the E3s Partitions

Hi Nick, > On Putty it just comes up with this and that's it.. > “Amstrad Delta - PBL V4.9 Build:1311 Assert Debug ICE > PBL 32MB NAND > 0MB.-->MEMv01.00.002,CopyLim=0022h,CodeEnd=0140h-->PBL..1MB...2MB*” > Dam have to buy another one now. I agree with David; PBL survives, by

Re: [E3-hacking] Understanding the E3s Partitions

Hi Nick, > root@amsdelta:~# cat /proc/mtd > dev: size erasesize name > mtd0: 0038 4000 "Kernel" > mtd1: 0004 4000 "u-boot" > mtd2: 0004 4000 "u-boot params" > mtd3: 0004 4000 "Amstrad LDR" > mtd4: 01b0 4000 "File system" > mtd5:

Re: [E3-hacking] Understanding the E3s Partitions

: Re: [E3-hacking] Understanding the E3s Partitions It's pretty hard to brick them --- PBL's in a different ROM chip to the main flash (and I think you can't reflash it anyway?), so even if you've trashed the main flash PBL runs. So, you should be able to connect pbltool or pblq to it and read

Re: [E3-hacking] Understanding the E3s Partitions

It's pretty hard to brick them --- PBL's in a different ROM chip to the main flash (and I think you can't reflash it anyway?), so even if you've trashed the main flash PBL runs. So, you should be able to connect pbltool or pblq to it and read and reflash, even if it doesn't boot. On Sat, 13 Apr

Re: [E3-hacking] Understanding the E3s Partitions

mtd0 Block Size 16384,Page Size 512, 00B Size 16 Dumping data starting at 0x and ending at 0x0038...* mtd1 Block Size 16384,Page Size 512, 00B Size 16 Dumping data starting at 0x and ending at 0x0004...* mtd2 Block Size 16384,Page Size 512, 00B Size 16 Dumping data starting

Re: [E3-hacking] Understanding the E3s Partitions

Dam..Just tried to flash the E3 and now it don’t boot, ah well..☹ With that's code and it starred coming up with “Flashing Data to NAND Flash without EEC in not recommended” On Putty it just comes up with this and that's it.. “Amstrad Delta - PBL V4.9 Build:1311 Assert Debug ICE PBL 32MB NAND

Re: [E3-hacking] Understanding the E3s Partitions

root@amsdelta:~# cat /proc/mtd dev: size erasesize name mtd0: 0038 4000 "Kernel" mtd1: 0004 4000 "u-boot" mtd2: 0004 4000 "u-boot params" mtd3: 0004 4000 "Amstrad LDR" mtd4: 01b0 4000 "File system" mtd5:

Re: [E3-hacking] Understanding the E3s Partitions

Its Cliff Lawson not Clive,who is Clive.. What Clive Sinclair …  “Aren't PBL and Uboot two distinct separate things?” Yes I know they are but mtd0 is where boot (like the bios on a PC) would be so PBL or Uboot would be there. Example..

Re: [E3-hacking] Understanding the E3s Partitions

Hi Nick, > if [ -e /media/sda1/e3-nand-backup.0 ]; then > echo Found e3-nand-backup.0 > echo " Erasing /dev/mtd0" > flash_erase /dev/mtd0 0 16 > echo " Writing e3-nand-backup.0 to /dev/mtd0" > nandwrite -on /dev/mtd0 /media/sda1/e3-nand-backup.0 > fi Parameterise the code to extract the

Re: [E3-hacking] Understanding the E3s Partitions

Hi Nick, > Mtd0,2,3,4,5 Size 16384,Page Size 512, 00B Size 16 > only need to restore mtd0,1,3 and 4 so ones with a * on. > mtd0: Dumping Data Starting at 0x and ending at 0x0030* > mtd1: Dumping Data Starting at 0x and ending at 0x0004* > mtd2: Dumping

Re: [E3-hacking] Understanding the E3s Partitions

Hi Nick, > mtd0 - kernel > mtd1 - PBL ( Maybe, I say this because Uboot is flashed there.) Aren't PBL and Uboot two distinct separate things? PBL was written by Clive at Amstrad. On the E2, it's the sole occupant of the small 64 KiB flash so it isn't at risk of corruption when it writes to the

Re: [E3-hacking] Understanding the E3s Partitions

Made a mistake.. ..☹ This at the end of the code e3-nand-backup.4, its says ” nandwrite -on /dev/mtd3 /media/sda1/e3-nand-backup.3” what it should be mtd4 and 4 at the end of this code “nandwrite -on /dev/mtd4 /media/sda1/e3-nand-backup.4” if [ -e /media/sda1/e3-nand-backup.4 ]; then echo

Re: [E3-hacking] Understanding the E3s Partitions

Can someone look at this… Just edited the ams-delta-install script and renamed it to ams-delta-restore-e3-install I can do all the work and tests, Just need a expert to look at the code and see if it OK because I am just reading up on MTD NAND write and dumping stuff on the net. This is how

Re: [E3-hacking] Understanding the E3s Partitions

Just copy the Amstrad Firmware to USB and as well flash Linux on the E3 so now I have to find a way to flash it back..  wow its takes a long time to boot, it took about a hour to copy the Amstrad Firmware over to USB.Is each file a copy of the partition(mtd0,1,2,3,4,5,) only mtd0,1,3 and 4 get

Re: [E3-hacking] Understanding the E3s Partitions

Oh one more thing.. the USB memory stick,does it matter if its fat or fat32 formatted to copy the 6 files over to it,it don’t say in the Readme..? Spanner.. From: Nick Griffin Sent: ‎Friday‎, ‎12‎ ‎April‎ ‎2019 ‎14‎:‎02 To: Discussion of the Amstrad E3 emailer

Re: [E3-hacking] Understanding the E3s Partitions

“When it flash's Linux to the E3 it only uses partitions mtd0,mtd1,mtd3 and mtd4, so mtd2 and mtd3 is not used.” mtd0 - kernel mtd1 - PBL ( Maybe, I say this because Uboot is flashed there.) mtd3 - ldr ( File System..? uses mtdblock3 of mtd3) mtd4 - Root( Root File System,maybe ?? uses mtdblock4