I also found two nicely compatible 8GBit TSOP48 Toshiba Flash Chips in a CNMemory 2GByte CF Card.

So I soldered one of the 8GBit chips on top of the already existing 512MBit chip (all signals except CE are shared).Soldering was a bitch though (pins did almost, but not quite reach the pins below), but with lots of solder, cursing, solderwick and patienceI eventually had all relevant pins connected. Since the Linux kernel unfortunately always enables/disables both CE signals I couldn't simply use the CE1 signal from the CPLD, but for now(first tests) I hooked up CE to the Cathode of the Green EMail-LED (which is normally always off and the transistor acts as an inverter, so'on' == low, exactly what I need) and a 10k pull-up.

The system boots fine and a hacked up 'fiddle with CEs and read IDs' kernel module finds both Chips just fine:

CODE

Trying to read id from Flash on CE0Got maker=98 device=76Trying to read id from Flash on CE1|GreenLEDGot maker=98 device=d3

According to drivers/mtd/nand/nand_ids.c maker 0x98 is 'Toshiba', device 0x76 is a 'NAND 64MiB 3,3V 8-bit' and device 0xd3 is the shiny new 'NAND 1GiB 3,3V 8-bit' (Yay!).

This should actually already exercise all control signals, so the only remaining task is to modify the built-in sharp_sl nand driver to properly support two chips.

Wow! Really nice mod. Is hacking the NAND driver a trivial matter (asking because from what I hear, Sharp did not release source files). Is hacking the driver the only thing that needs to be done to have the Zaurus see and use the new NAND storage as ROM? Would love to see a screenshot of System Properties showing all that internal memory.

If you pre-tin the new memory chip leads, would that extend them enough to make soldering less risky?

Wow! Really nice mod. Is hacking the NAND driver a trivial matter (asking because from what I hear, Sharp did not release source files). Is hacking the driver the only thing that needs to be done to have the Zaurus see and use the new NAND storage as ROM? Would love to see a screenshot of System Properties showing all that internal memory.

The nand driver is included in the sharp source tree (or in the cacko source tree, for that matter).Hacking the driver shouldn't be too difficult, I hope to find the time to do that the coming weekend.The hacked driver would expose the NAND as just another mtd partition, which can then be formatted using JFFS2.Using a FS not specifically designed for flash would also be possible, but a big "don't do that" since ther is no wear-leveling. Unfortunately JFFS2 does not perform well with big filesystem sizes, maybe I'll try YAFFS instead.

QUOTE

If you pre-tin the new memory chip leads, would that extend them enough to make soldering less risky?

Maybe.I think applying flux to the old chip leads may also help a lot.

Interesting tidbits:dd if=/dev/mtdblock of=/dev/null clocks in at about 2MB/s (on the 64MB flash)This corresponds nicely to a benchmark I did on the PIO reads from the CPLD, however if I use the pxa dma engine I can read at >10MB/s.

Hooking up the chip-enable to the green led is just a temporary measure, I'm thinking of hooking it up using a transistor, with the base connected to CE0 using a resistor,the emitter connected to CE1 an the collector connected to CE (while also leaving the pull-up in place).

This should act so that a low-level on CE1 gets only passed on to CE if CE0 is high-level and so works around the 'Sharp Kernel turns on/off both CE0 and CE1'.

I thought long ago someone was stating that 128MB RAM was possible with the Z.

I think it was Speculatrix who (unsuccessfully) tried that. Brave soul. It would have been a success but the chip cracked, or something like that.

no, I was trying to fit a bluetooth module inside my sl-6000, turned out I had the wrong type of module - there are many variants of Mitsumi devices. in the process of reassembling it I was squeezing the USB wifi module on and snapped a RAM chip. I tried to find someone who could do BGA "surgery" to remove the bust ram chip and fit a new one, and possibly populate the empty slots for more memory too.

that zaurus is still b0rked - the person capable of BGA surgery was unavailable and the RAM chips are very hard/impossible to find.

I thought long ago someone was stating that 128MB RAM was possible with the Z.

I think it was Speculatrix who (unsuccessfully) tried that. Brave soul. It would have been a success but the chip cracked, or something like that.

no, I was trying to fit a bluetooth module inside my sl-6000, turned out I had the wrong type of module - there are many variants of Mitsumi devices. in the process of reassembling it I was squeezing the USB wifi module on and snapped a RAM chip. I tried to find someone who could do BGA "surgery" to remove the bust ram chip and fit a new one, and possibly populate the empty slots for more memory too.

that zaurus is still b0rked - the person capable of BGA surgery was unavailable and the RAM chips are very hard/impossible to find.

Maybe a cheap motherboard to replace borked one. Been a while since that ad, but I just now remembered seeing it.

thanks, but I did buy a b0rked 6000, a guy dropped it off the roof of his house (I've never found out why he was up there with his Z!), the screen broke but the motherboard survived! I've still got problems with its LCD connector, it needs refixing. Also my batteries are shot. I recently bought a Dlink DSM-G600 wifi hard drive thing which I intend to fit in the car and use the Z as a media player using samba over wifi.

The nand driver is included in the sharp source tree (or in the cacko source tree, for that matter).Hacking the driver shouldn't be too difficult, I hope to find the time to do that the coming weekend.The hacked driver would expose the NAND as just another mtd partition, which can then be formatted using JFFS2.Using a FS not specifically designed for flash would also be possible, but a big "don't do that" since ther is no wear-leveling. Unfortunately JFFS2 does not perform well with big filesystem sizes, maybe I'll try YAFFS instead.

Well, it took a bit longer than expected, but it is basically working now.I can mount jffs2 and read/write to the partition.I get occasional crc errors though (probably because I commented out the write verification code, that is not converted yet).For testing I only used 128MB instead of the full size:

Interesting tidbits:dd if=/dev/mtdblock of=/dev/null clocks in at about 2MB/s (on the 64MB flash)This corresponds nicely to a benchmark I did on the PIO reads from the CPLD, however if I use the pxa dma engine I can read at >10MB/s.

Well, slight problem with trying to use dma: Apparently I overread the part where the docs state that byte-reads are only allowed for on-chip peripheralsand all external reads have to be 8-byte aligned. Unfortunately the data register is not 8-byte aligned and only byte-readable.

Aligned dma copies from/to the w100 framebuffer seem to work fine though (didn't get much testing though).

The RAM upgrade is hard simply because it's in a BGA package which needs hot-air rework equipment and no fear. I seem to recall Maslovsky had a few done.

- 'Twere he. Saint Maslovsky has a C750 w/ 128MB RAM and was working on the C1000 about the time Cacko 1.23 was released. Since then he evaporated, seemingly. Hope he's okay and all.- I like the GB flash mod. I could fit Debian in that and not worry about stuffing it on an SD card. Nice! Now if I could just work up the courage to rip Hiro apart and go at him with heat and purpose. (owlish stare)