LeapFrog Pollux Platform: DFTPdevice - Revision history

Jrspruitt: /* Versions */

2013-02-14T02:15:45Z

‎Versions

Jrspruitt: /* Connection */

2013-02-11T05:31:51Z

‎Connection

Jrspruitt: /* Versions */ changed table formatting on page

2013-02-11T05:29:45Z

‎Versions: changed table formatting on page

Jrspruitt: /* Connection */ Updated for DFTP Version 4

2013-02-11T05:17:33Z

‎Connection: Updated for DFTP Version 4

Jrspruitt: /* Versions */ Upated DFTP versions

2013-02-11T04:58:13Z

‎Versions: Upated DFTP versions

Jrspruitt: /* Explorer */

2012-11-12T22:13:32Z

‎Explorer

Jrspruitt at 22:02, 12 November 2012

2012-11-12T22:02:34Z

Jrspruitt at 23:43, 4 February 2012

2012-02-04T23:43:29Z

Jrspruitt at 23:27, 4 February 2012

2012-02-04T23:27:49Z

Jrspruitt: /* DFTP Device */

2012-02-04T23:25:40Z

‎DFTP Device

@@ Line 60: / Line 60: @@
 |-
-!colspan="3"|Firmware < 2.4.10.3030
+!colspan="3"|Firmware < 2.2.4-3609
 |-
@@ Line 78: / Line 78: @@
 |-
-!colspan="3"|Firmware >= 2.4.10.3030
+!colspan="3"|Firmware >= 2.2.4-3609
 |-

@@ Line 120: / Line 120: @@
 Write(10) and read(10) SCSI commands are used exclusively. There is one vendor specific command that is sent, C2 with CDB length of 10, all 0x00, but seems to have no effect on the device. Write(10) and Read(10) are used in pairs for most commands, uploading or download data is the exception read or write is repeated until data sent.
-If you write to LBA 0x20, you must read your response from it also. Transfer Length dictates the size of packets you send. Regular commands are 0x01 or 512 bytes, large data is transferred in 0x14 or 10240 bytes. All data must be aligned to this size, padded with 0x00 when necessary. When done a 101 EOF:<padding size> command is sent/received, to determine if the last packet needs to be trimmed.
+If you write to LBA 0x20, you must read your response from it also. Transfer Length dictates the size of packets you send. Regular commands are 0x01 or 512 bytes, large data is transferred in 0x14 or 10240 bytes. All data must be aligned to this size, padded with 0x00 when necessary. When done a 101 EOF:<padding size> response code is sent/received, to determine if the last packet needs to be trimmed.
 == Response Codes ==

@@ Line 4: / Line 4: @@
 There are currently 2 versions of DFTPdevice, 1.12, mostly used in Surgeon, and 1.8 for firmware. The Explorer and LeapPad version, while containing the same version number, do seem to differ, most notably in that if you disconnect from the Explorer version it reboots, while the LeapPad version goes back to broadcasting its address, waiting for another connection.
 {| border="1" cellpadding="5" cellspacing="0"
@@ Line 48: / Line 51: @@
 |4
 |}
@@ Line 84: / Line 89: @@
 |English
 |4
 |}

@@ Line 88: / Line 88: @@
 == Connection ==
-When the device starts it opens port 5000, once you make a socket connection, you then need to send the ETH command and wait a second or two. The device then opens up a socket to port 5001, make your second connection to this port, and you can then start communicating with it.
+'''Version 1.x'''
 is the port you send commands to.
@@ Line 94: / Line 96: @@
 is the port you read the responses from.
 == Response Codes ==

@@ Line 7: / Line 7: @@
 {| border="1" cellpadding="5" cellspacing="0"
 !colspan="3"|Explorer
 |-
@@ Line 32: / Line 35: @@
 |French
 |1.8
 |}
@@ Line 38: / Line 53: @@
 {| border="1" cellpadding="5" cellspacing="0"
 !colspan="3"|LeapPad
 |-
@@ Line 53: / Line 71: @@
 |English
 |1.12
 == Connection ==

@@ Line 346: / Line 346: @@
 === Explorer ===
-The Explorer uses a combination of the file names, and a file system map file on the device itself, either if running Surgeon or booted normally, to allow dftpdevice to successfully update the firmware.
+The Explorer uses a combination of the file names, and a file system map file on the device itself, to allow dftpdevice to successfully update the firmware.
 ==== Firmware File Names ====

← Older revision		Revision as of 22:02, 12 November 2012
Line 340:		Line 340:

	DCON		DCON
		+
		+
		+	== Firmware Updates ==
		+	DFTP's main purpose is for Firmware updating by LFConnect. Basically there is a set of special folders created on the device by dftpdevice, which are uploaded to. This triggers the upload to be written to the NAND, instead of to Surgeon's RAM file system. For the Explorer DFTP is used exclusively for this purpose. While the LeapPad uses a program called Fuse-Flasher that can be found in [source]/packages.
		+
		+	=== Explorer ===
		+	The Explorer uses a combination of the file names, and a file system map file on the device itself, either if running Surgeon or booted normally, to allow dftpdevice to successfully update the firmware.
		+
		+	==== Firmware File Names ====
		+	The firmware file names are used by dftpdevice to figure out where to flash the data to on NAND. This will write the data to that location regardless of the fs map. But will cause issues with UBI images if not coordinated with the map. 131072 is the PACKETSIZE returned in the INFO command.
		+
		+	Format: [NAND Address],[Partition Size/131072],[Filename]
		+
		+	Example:
		+	1048576,8,FIRST.32.rle
		+	2097152,64,kernel.cbf
		+	10485760,688,erootfs.ubi
		+	100663296,15616
		+
		+
		+	==== Device FS Map ====
		+
		+	On the device itself there is a list of files in /var with extension .fs. These numbers are used in the creation of the mtd/ubi devices required for mounting and flashing. To figure out which version your firmware is using, take a look at /etc/init.d/recover-mounts. In that script there is a variable fs, near the beginning, that shows which file to use.
		+
		+	Format: [NAND Address] [Partition Size] [Filename]
		+
		+	Example:
		+	0x00000000 0x00100000 payload/emerald-boot.bin
		+	0x00100000 0x00100000 payload/FIRST.32.rle
		+	0x00200000 0x00800000 payload/kernel.cbf
		+	0x00a00000 0x05600000 payload/erootfs.ubi
		+	0x06000000 0x7a000000 payload/bulk.ubi
		+
		+	==== Altering Partitions ====
		+	To change the partitions, a few things need to be accomplished before configuring dftpdevice. The kernel has the partitions hard coded into it, those will need to be changed. And if you move the kernel, Emerald Boot will need to be compiled with the new kernel address and size.
		+
		+	Once those are taken care of, you will need to calculate the file names, and create the new .fs file. From my experience the .fs is most critical for UBI, as once Emerald Boot was compiled with the proper kernel address, it loaded fine. But for UBI there are certain steps required for flashing to NAND, like erase counter management and it's lack of OOB usage, that need to be dealt with. dftpdevice will write the UBI image where ever the file name numbers tell it too, but it will not be usable by the kernel. If you get an error 22 manually mounting it, this is probably the reason. An MTD and UBI device needs to be created for proper flashing, which dftpdevice creates the MTD devices using the .fs file information. For more application of this, look in /etc/init.d/recovery-mounts.

← Older revision		Revision as of 23:43, 4 February 2012
Line 1:		Line 1:
−	~~Work in progress, just jotting down notes currently.~~
−
	DFTPdevice is a custom server LeapFrog includes with the [[Leapster_Explorer\|Explorer]] and [[LeapPad_Explorer \| LeapPad]]. This is the main interface between LFConnect, and these devices. DFTPdevice seems loosely based on an FTP server, while including customized features for the purposes of updating the firmware, and a general maintenance.		DFTPdevice is a custom server LeapFrog includes with the [[Leapster_Explorer\|Explorer]] and [[LeapPad_Explorer \| LeapPad]]. This is the main interface between LFConnect, and these devices. DFTPdevice seems loosely based on an FTP server, while including customized features for the purposes of updating the firmware, and a general maintenance.

@@ Line 2: / Line 2: @@
 DFTPdevice is a custom server LeapFrog includes with the [[Leapster_Explorer|Explorer]] and [[LeapPad_Explorer | LeapPad]]. This is the main interface between LFConnect, and these devices. DFTPdevice seems loosely based on an FTP server, while including customized features for the purposes of updating the firmware, and a general maintenance.
 == Versions ==
@@ Line 65: / Line 56: @@
 |1.12
 |}
 == Response Codes ==

← Older revision		Revision as of 23:25, 4 February 2012
Line 2:		Line 2:

	DFTPdevice is a custom server LeapFrog includes with the [[Leapster_Explorer\|Explorer]] and [[LeapPad_Explorer \| LeapPad]]. This is the main interface between LFConnect, and these devices. DFTPdevice seems loosely based on an FTP server, while including customized features for the purposes of updating the firmware, and a general maintenance.		DFTPdevice is a custom server LeapFrog includes with the [[Leapster_Explorer\|Explorer]] and [[LeapPad_Explorer \| LeapPad]]. This is the main interface between LFConnect, and these devices. DFTPdevice seems loosely based on an FTP server, while including customized features for the purposes of updating the firmware, and a general maintenance.
−
−	~~== DFTP Device ==~~
−	DFTPDevice is included in both LeapPad and Explorer versions of Surgeon.cbf and their respective firmwares. Surgeon's come with version 1.12, although there seems to be a slight difference in the two, as Explorer Surgeon will reboot if you destroy the sockets connected to it, LeapPad's will reset the DFTPDevice and got back to broadcasting its IP address. Explorer firmware contains version 1.18.
−	~~TODO: Get LeapPad's version number~~