Joggler - Recent changes [en-gb]

User:Peter kemm

2012-05-18T18:03:48Z

Peter kemm created a user account

User:Tsi.swisscom

2012-05-15T21:10:00Z

Tsi.swisscom created a user account

User:Paulsbiz

2012-05-11T19:55:47Z

Paulsbiz created a user account

User:The spudster

2012-05-10T23:02:15Z

The spudster created a user account

Using the Joggler as a VGA/DVI screen

2012-05-06T16:28:59Z

File:LVDS24-01.jpg

2012-05-06T15:11:47Z

Inaxeon uploaded "File:LVDS24-01.jpg"

File:Joggler d945gsejt.jpg

2012-05-06T15:11:06Z

Inaxeon uploaded "File:Joggler d945gsejt.jpg"

File:D945gsejt lvds.jpg

2012-05-06T15:10:32Z

Inaxeon uploaded "File:D945gsejt lvds.jpg"

Native Applications

2012-05-04T11:02:18Z

‎Utilities:

User:Richmac

2012-05-04T10:56:17Z

Richmac created a user account

EFI

2012-05-02T10:36:11Z

Using the Joggler as a VGA/DVI screen

2012-05-02T09:22:15Z

User:Pokersut

2012-04-28T09:39:03Z

Pokersut created a user account

Ubuntu Internal emmc

2012-04-22T19:01:54Z

‎Part 1:

Show changes

Howto customise the boot logo

2012-04-21T07:15:16Z

‎Method 2 - with flashrom in a ubuntu/debian etc environment:

@@ Line 40: / Line 40: @@
 Stranger still, this doesn't seem to be a problem I've introduced, all firmware images with pixel clocks under 60MHz have this problem which is making me wonder if there is some subtle hardware modification required on this board for smaller panels. Time will tell.
-'''UPDATE:'''
+'''UPDATE (16/04/2012):'''
 After almost a year of hacking the LCD Controller firmware, I finally have a picture on the Joggler's LQ070Y3LG4A LCD panel.
 It's not perfect, but it's getting there!
 [[File:lcdcontroller_working.jpg]]
 [[File:lcdcontroller_closeup.jpg]]
 Questions: mailto:inaxeon@hotmail.com

@@ Line 9: / Line 9: @@
 === Internet ===
-* [http://www.joggler.info/forum/viewtopic.php?f=24&t=823 Running Opera Mobile web browser]
+* [http://www.jogglerwiki.com/forum/viewtopic.php?f=24&t=823 Running Opera Mobile web browser]
 === Utilities ===
 * [[Remote_Desktop|Installing Remote Desktop]]

@@ Line 1: / Line 1: @@
 It is important to distinguish between the EFI system that starts when you power on the Joggler, and the [[boot loader]] that then goes on to load your chosen OS. It may be useful to read the [http://en.wikipedia.org/wiki/Extensible_Firmware_Interface EFI page on Wikipedia] for a grounding.
-When power is applied to a Joggler the firmware starts the EFI environment, which has been preprogrammed from the factory to look for devices to boot from. This includes USB-attached devices, presumably to allow for recovery in case of damage to the native operating system. USB devices are booted in preference to the internal flash, allowing us to start an alternative OS without altering the internal one.
+When power is applied to a Joggler the firmware starts the EFI environment, which has been preprogrammed from the factory to look for devices to boot from. This includes USB-attached devices, which allows for recovery in case of damage to the native operating system.
-In order to boot, the first partition of the USB device must be FAT formatted (officially FAT16 is preferred) and around 64MB in size. Smaller sizes work reliably, while larger partitions (eg. 128MB) have been known to fail. The files '''startup.nsh''' and '''boot.nsh''' are then used to control what happens next. By convention, '''startup.nsh''' is executed first.
+Although USB devices appear to be booted in preference to the internal flash, it is often the case that the internal flash simply redirects to the external device should one be present (hence the two entries in '''startup.nsh''', explained below). This allows us to start an alternative OS without altering the internal one. Happily, should the internal flash fail (which is a common fault) the EFI environment simply moves on to the next available storage device.
 == Boot Components ==
 === startup.nsh ===
-Ordinarily, '''startup.nsh''' contains the following:
+By default, '''startup.nsh''' on the internal flash contains the following:
   fs1:boot2
   fs0:boot
-I have yet to find an explanation for the first line, as it refers to filesystem 1 and a file called boot2.nsh, which we do not have. In my experiments the file can be pared down to:
+The first line attempts to call '''boot2.nsh''' on an external device, which will normally fail. It then continues to execute '''boot.nsh''' on the primary device (itself).
   fs0:boot
-Which makes more sense, at least to me. Unsurprisingly, this triggers '''boot.nsh''' on filesystem 0.
+This will attempt to call '''grub''' on an external device, before loading from the internal flash. It's a sensible precaution to take should the internal flash give up and will save you from having to mash <ESCAPE> on your keyboard to get an external device to boot.
 === boot.nsh ===
@@ Line 34: / Line 39: @@
   cd \efi\grub
   grub
 === grub.cfg ===

← Older revision		Revision as of 09:22, 2 May 2012
Line 49:		Line 49:

	[[File:lcdcontroller_closeup.jpg]]		[[File:lcdcontroller_closeup.jpg]]
−
−	~~Newly written programmer software:~~
−
−	~~[[File:lcdcontroller_rovatool.jpg]]~~
−
−	~~Firmware descrambler:~~
−
−	~~[[File:lcdcontroller_gff2bin.jpg]]~~

	Questions: mailto:inaxeon@hotmail.com		Questions: mailto:inaxeon@hotmail.com

@@ Line 30: / Line 30: @@
 This tool extracts all the content of the EFI. I have made a quick python script that utilises the Huffman decompression algorithm provided by it to decompress the one bit of the EFI we are interested in. The efidump.py tool is then only needed at the very end as a basic test that our resulting modified image might work.
-Create a new file, call it efidecompress.py and put the following in it (you may need to remove an additional space from the beginning of each line, a side effect of copy/pasting from wiki), then make it executable.
+Create a new file, call it efidecompress.py and put the following in it, then make it executable.
- #!/usr/bin/python
+import EfiDecompressor
- # -*- coding: utf-8 -*-
- import sys
- import struct
-−
- import EfiDecompressor
-−
- def savedata(name, data):
-   outstream = open(name, "wb")
-   outstream.write(data)
-   outstream.close()
-−
- instream = open(sys.argv[1])
- instream.seek(0, 2)
- streamlength = instream.tell()
- instream.seek(0, 0)
-−
- compressed = instream.read(streamlength)
- efidecompressed = EfiDecompressor.Decompress(compressed)
- savedata(sys.argv[2],efidecompressed)
 ==EFI Huffman/Tiano Compressor ==
@@ Line 70: / Line 70: @@
 If you don't have it already you can obtain it as follows :
 )boot the joggler on stock firmware with the “telnet hack” enabled. Google “joggle telnet hack” if you don't know what this is.
@@ Line 76: / Line 80: @@
 )Insert a USB storage device with at least 1 meg free space and copy the EFI image to it : “dd if=/dev/fh of=/mnt/efi.bin bs=1024k”
 ===Part B) – Extract the driver file===