Sharp Mobilion Pro PV5000A - Revision history

Sjlongland: /* System Specifications */

2005-11-30T05:55:01Z

‎System Specifications

Sjlongland: /* News */ NetBSD/hpcmips works! :-D

2005-11-30T03:00:22Z

‎News: NetBSD/hpcmips works! :-D

Sjlongland: /* System Specifications */

2005-10-29T04:25:27Z

‎System Specifications

Sjlongland: /* 28/10/2005: Locating the JTAG Interface */

2005-10-29T02:59:05Z

‎28/10/2005: Locating the JTAG Interface

Sjlongland: /* 28/10/2005: Locating the JTAG Interface */

2005-10-29T02:58:42Z

‎28/10/2005: Locating the JTAG Interface

Sjlongland: /* 28/10/2005: Locating the JTAG Interface */

2005-10-29T02:57:01Z

‎28/10/2005: Locating the JTAG Interface

Sjlongland: /* News */

2005-10-28T10:49:06Z

‎News

Sjlongland at 13:59, 22 September 2005

2005-09-22T13:59:23Z

Alec v: DRAM datasheet

2005-09-22T09:45:14Z

DRAM datasheet

Alec v: S1D13504

2005-08-17T20:25:28Z

S1D13504

@@ Line 54: / Line 54: @@
 = System Specifications =
-* CPU: Toshiba [[TX39XX|TX3922]] 129MHz [[Instruction_Set_Architecture|MIPS 1]].  Little Endian.
+* CPU: Toshiba [[TX39XX|TX3922]] 129MHz [[Instruction_Set_Architecture|MIPS 2]].  Little Endian.
 * RAM: 32MB
 * ROM: 16MB (Estimated) has Windows CE and numerous applications burned in.

← Older revision		Revision as of 03:00, 30 November 2005
Line 1:		Line 1:
	= News =		= News =
		+	== 30/11/2005: Got NetBSD/hpcmips running ==
		+
		+	After some 130MB or so of downloads, several hours, and getting a crash-course in cross-compiling NetBSD... I managed to compile a NetBSD kernel that boots on this device.
		+
		+	[http://dev.gentoo.org/~redhatter/mips/hpc/sharp_mp_pv5000a/netbsd/ Here] you'll find my kernel (netbsd.gz) and config (TX3922-ramdisk.gz, based on TX3922). Drop these on a CF card (or download them across a network, or upload via serial link... whatever floats your boat), along with [ftp://ftp.netbsd.org/pub/NetBSD-daily/netbsd-3/200511140000Z/hpcmips/installation/hpcboot.exe hpcboot] and [ftp://ftp.netbsd.org/pub/NetBSD-daily/netbsd-3/200511140000Z/hpcmips/installation/miniroot/miniroot.fs.gz this ramdisk image].
		+
		+	Then, on the device, fire up hpcboot. Select ''md'' as your root device, and enter ''miniroot.fs'' (or .gz if you haven't decompressed it). Select "boot verbosely" and "serial console 9600", then plug in your sync cable, fire up a serial terminal program (e.g. minicom; 9600 baud, 8N1) and hit BOOT on the device. You should see NetBSD start booting after a few seconds.
		+
		+	Having a kernel which boots, means it should be only a little more work to get Linux doing the same thing. I can boot to a shell via NetBSD. I haven't got PCMCIA working just yet, but I hope to get something going in the next few weeks as I tinker.

	== 28/10/2005: Locating the JTAG Interface ==		== 28/10/2005: Locating the JTAG Interface ==

@@ Line 48: / Line 48: @@
 * RAM: 32MB
 * ROM: 16MB (Estimated) has Windows CE and numerous applications burned in.
-* Framebuffer: 640x480 12-bit colour.  Unknown chipset.
+* Framebuffer: 640x480 12-bit colour.  Epson Chipset (see below)
 I/O Peripherals:

← Older revision		Revision as of 02:59, 29 October 2005
Line 8:		Line 8:

	These are the pins where I suspect the JTAG resides:		These are the pins where I suspect the JTAG resides:
		+
	[[Image:Mobilion_pro_jtag.jpg]]		[[Image:Mobilion_pro_jtag.jpg]]

@@ Line 7: / Line 7: @@
 After my exams, I'll look into it.  I found a datasheet on the CPU [http://www.toshiba.com/taec/components/Datasheet/TX3922ds.pdf here], which I will naturally have a close look at.  Pins 30 ~ 34 may have something to do with it.  Here's hoping that's the case. :-)  Of course mearly having a JTAG isn't good enough -- one must know what to do with it.  That is the next step.
-I have drawn up a diagram showing the JTAG pins here: [[Mobilion_pro_jtag.jpg]]  This is a large image, be warned.
+These are the pins where I suspect the JTAG resides:
 == 14/08/2005: Obtaining the tools & my plans ==

← Older revision		Revision as of 02:57, 29 October 2005
Line 6:		Line 6:

	After my exams, I'll look into it. I found a datasheet on the CPU [http://www.toshiba.com/taec/components/Datasheet/TX3922ds.pdf here], which I will naturally have a close look at. Pins 30 ~ 34 may have something to do with it. Here's hoping that's the case. :-) Of course mearly having a JTAG isn't good enough -- one must know what to do with it. That is the next step.		After my exams, I'll look into it. I found a datasheet on the CPU [http://www.toshiba.com/taec/components/Datasheet/TX3922ds.pdf here], which I will naturally have a close look at. Pins 30 ~ 34 may have something to do with it. Here's hoping that's the case. :-) Of course mearly having a JTAG isn't good enough -- one must know what to do with it. That is the next step.
		+
		+	I have drawn up a diagram showing the JTAG pins here: [[Mobilion_pro_jtag.jpg]] This is a large image, be warned.

	== 14/08/2005: Obtaining the tools & my plans ==		== 14/08/2005: Obtaining the tools & my plans ==

← Older revision		Revision as of 10:49, 28 October 2005
Line 1:		Line 1:
	= News =		= News =
		+
		+	== 28/10/2005: Locating the JTAG Interface ==
		+
		+	Looking at [http://openwince.sourceforge.net/jtag/iPAQ-3600/ this page], it seems somewhere on the mainboard, they'll be some pads, to which I can wire a JTAG Interface. Now, I've got some pretty clear shots of the CPU on my devspace (see my raw pictures -- hpim0527.jpg is a particularly detailed shot of the CPU), it's just a matter of finding out what each and every pin does. In addition, more challenges lay ahead -- these pins are very bloody close together, and my chances of hitting one the wrong way are extremely high. I've touched this board with a soldering iron before -- but that was to fix a power socket with nice chunky connections -- this is much smaller again. I may require a new soldering iron for the task.
		+
		+	After my exams, I'll look into it. I found a datasheet on the CPU [http://www.toshiba.com/taec/components/Datasheet/TX3922ds.pdf here], which I will naturally have a close look at. Pins 30 ~ 34 may have something to do with it. Here's hoping that's the case. :-) Of course mearly having a JTAG isn't good enough -- one must know what to do with it. That is the next step.

	== 14/08/2005: Obtaining the tools & my plans ==		== 14/08/2005: Obtaining the tools & my plans ==

← Older revision		Revision as of 13:59, 22 September 2005
Line 199:		Line 199:

	The only ICs I've identified thus far are the CPU and the LCD controller... although I'll be pestering Google for info on the others shortly.		The only ICs I've identified thus far are the CPU and the LCD controller... although I'll be pestering Google for info on the others shortly.
		+
		+	===Links===
		+
		+	1. http://www.realitydiluted.com/projects/nino/port/remove-rom.html describes the ROM in a similar device. The ROM used on the Mobilion PRO above is almost identical (other than the fact that the plug is in a different location) This site also describes how to potentially erase and reprogramme the flash chips used on this ROM. This opens the possibility of completely ridding WinCE for good. :-)

@@ Line 95: / Line 95: @@
 </td>
 <td>
-DRAM/FLASH Memory ?
+Toshiba EDO DRAM 64Mbit (4Mx16bit) Memory
 </td>
 </tr>
@@ Line 105: / Line 105: @@
 </td>
 <td>
-DRAM Memory ?
+Hitachi [http://jastronic.com/Datasheet/EDO/H_EDO/HM5165165.pdf EDO DRAM] 64Mbit (4Mx16bit) Memory
 </td>
 </tr>
@@ Line 154: / Line 154: @@
 </td>
 <td>
-DRAM/FLASH Memory ?
+Hitachi [http://jastronic.com/Datasheet/EDO/H_EDO/HM5165165.pdf EDO DRAM] 64Mbit (4Mx16bit) Memory
 </td>
 </tr>
@@ Line 165: / Line 165: @@
 </td>
 <td>
-DRAM Memory ?
+Toshiba EDO DRAM 64Mbit (4Mx16bit) Memory
 </td>
 </tr>

@@ Line 116: / Line 116: @@
 </td>
 <td>
-LCD Controller (now called S1D13504)
+LCD Controller (now called [http://www.erd.epson.com/vdc/html/S1D13504.html S1D13504])
 </td>
 </tr>