• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1] 2 3 ... 10
Author Topic: New QT based installer: Easy Plug Computer Installer (ESIA)  (Read 74677 times)
rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« on: March 01, 2010, 03:30:51 AM »

Hi all,

There is a new installer that is QT based, supported by the following x86 OSes:
- Fedora11 (32/64bit)
- Ubuntu 9.04 (32bit)
- Windows XP SP2/3 (32bit), Vista and w7 do work but been reported to have problems when installing libusb!! at your own risk
- OSX (Leopard)

In short this utility enables you to:
1) use it with any FTDI device (configurable VID/PID)
2) burn uboot to nand flash (set the MAC address too)
3) burn kernel+modules+distro to nand/mmc
4) all binaries (except of uboot) are validated on x86 machine using MD5
5) backup nand/mmc to USB DOK

The project is @ http://sourceforge.net/projects/esia/ and sources are posted later on as LGPL license.

Following are the basic docs you should read before using the ESIA:
- http://sourceforge.net/projects/esia/files/docs/ESIA_Project_Description.pdf/download
- http://sourceforge.net/projects/esia/files/docs/v2.0.2/ESIAv2_Quick_Start_Guide.pdf/download

OSX users should also read the http://sourceforge.net/projects/esia/files/docs/osx/ESIAv2_Apple_OSX_Quick_Start_Guide.pdf/download
W7 users should also read the  http://sourceforge.net/projects/esia/files/docs/win/ESIAv2_Microsoft_W7_Quick_Start_Guide.pdf/download

There are some known issues with this version, see them @ http://sourceforge.net/projects/esia/files/docs/v2.0.2/ESIAv2_test_matrix.pdf/download

I hope it make fresh plug burning a better experience for you  Smiley

more to come:
- freeBSD burning to mmc support
« Last Edit: August 18, 2010, 10:22:56 PM by rooster » Logged

marcus
Jr. Member
**

Karma: 5
Posts: 83


View Profile
« Reply #1 on: March 02, 2010, 01:38:22 AM »

Under Ubuntu 9.04 gives error upon (attempted) installation:

Code:
Error: Dependency is not satisfiable: libftdi1 (>= 0.16)

9.04 does not offer this version of libftd1. Solution: Upgrade to 9.10.

Under 9.10, started up esia with
Code:
gksudo esia
(I didn't see this in any of the documentation). Looks fine but won't have the chance to play with it for a day or two.

Looks very interesting. Thank you very much.
« Last Edit: March 02, 2010, 01:49:07 AM by marcus » Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #2 on: March 02, 2010, 02:35:53 AM »

ESIA was tested on 9.10 (see the test matrix pdf), regarding the sudo, you r right, it is missing from the documentation.

Thanks  Smiley
Logged

Abra
Newbie
*

Karma: 1
Posts: 29


View Profile
« Reply #3 on: March 03, 2010, 05:47:09 PM »

very nice.
can it flash uboot if the plug is bricked (bad uboot)?
thanks
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #4 on: March 04, 2010, 01:15:52 AM »

Yes, it supports uboot burning try it out.
Logged

djrm
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #5 on: March 04, 2010, 02:36:17 AM »

Greetings, I've just installed the windows version but unfortunateley it has disabled all the USB devices on my PC, havn't had time to investigate yet. I'll plug a PS2 mose in when I get home ...
Best regards, David.
Logged

superpat
Full Member
***

Karma: 15
Posts: 141


View Profile
« Reply #6 on: March 04, 2010, 08:12:19 AM »

Hi rooster

I have installed ESIA on Debian squeeze, and read several times the "quick start" guide.

It appears very complex to set up the files to burn to the Sheevaplug.

By the look and feel of ESIA  it was intended for S/W retailers to sell down loadable apps to run on a customers Sheevplug with remote purchase.

Regarding the ESIA app itself.

1. I cannot get the Device page to display any info on my plug, it can "see" it but all the details are N/A. Does this work yet?

2.  Reading the instructions, it seems that I HAVE to install a USB stick on the Sheevaplug on all operations, even if I am loading  a kernel from a "web" address.   The sheeva plug has to load  something from the USB stick that enables it to d/l from an IP address      HOW? WHY?  If the final D/L fails, does the plug get restored to the original state?

3.  How can I set load addresses for the down loadable information.  i.e. how do I set parameters?

4. Can I  build systems on SD and USB sticks or is  ESIA limited to D/L to nand?

5. If I just want to reload a new uboot.bin, where do I put it?  Do I need to build the complete "app" directory
structure?

6. Can this do a "bare iron" re-install or does the Plug have to be running a system?

7. Why can't the ESIA generate the md5 checksums, instead of the user having to do it?

regards

Patrick
 

Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #7 on: March 04, 2010, 12:59:01 PM »

Hi superpat,

Regarding the USB DOK setup, you basically need to place one of the distro tarballs on the DOK (un-tarred), the rest was already done for you. Use it as a reference if you like.
The ESIA is basically based on the sheeva Installer but extends the usability by allowing users to place different distros on the DOK and install one that they like.

There are several potential users:
1) plug newBs that wana try some distro out
2) potential customers that can use the web based installation scheme

Quote
1. I cannot get the Device page to display any info on my plug, it can "see" it but all the details are N/A. Does this work yet?
This could be tricky since the ESIA tries to intercept the uboot reboot countdown, you can try reset and click on the rescan button from the menu bar. I find the best way to close the ESIA , open a console and manage to stop the uboot countdown, then close the console application and open the ESIA .

Quote
2.  Reading the instructions, it seems that I HAVE to install a USB stick on the Sheevaplug on all operations, even if I am loading  a kernel from a "web" address.   The sheeva plug has to load  something from the USB stick that enables it to d/l from an IP address      HOW? WHY?  If the final D/L fails, does the plug get restored to the original state?

The ESIA uses the DOK as the way to transfer the binaries to the plug, if you only need to update the kernel I would just wget it, the ESIA is best for uboot burning and full distro burn. You could also upload the distro from the plug (backup option), place the new kernel in the backuped image and burn it back but that seems to me like a waist of time.
The backup option is not functional so it is not an option now.

Quote
3.  How can I set load addresses for the down loadable information.  i.e. how do I set parameters?

If you referring to load addresses, you would need to modify the ESIA source code, there is no configurable option.

Quote
4. Can I  build systems on SD and USB sticks or is  ESIA limited to D/L to nand?

The ESIA supports burning the kernel/distro to nand/mmc.

Quote
5. If I just want to reload a new uboot.bin, where do I put it?  Do I need to build the complete "app" directory
structure?

Place the new uboot in the c:\Program Files\ESIA\uboot\uboot.bin directory (or the equivalent path in Linux based ESIA installation)

Quote
6. Can this do a "bare iron" re-install or does the Plug have to be running a system?

The plug does not have to be running anything, it can be bricked. The ESIA sets the uboot parameters to make the plug load the initrd from USB and continue burn operation as was done by the Sheeva Installer.

Quote
7. Why can't the ESIA generate the md5 checksums, instead of the user having to do it?
The reason for this is that we assume you downloaded the kernel/distro and should have downloaded the md5 too, the ESIA perform validation of this MD5. If it was doing the MD5 there would not be any validation on the binaries.
Logged

marcus
Jr. Member
**

Karma: 5
Posts: 83


View Profile
« Reply #8 on: March 05, 2010, 05:51:42 PM »


Quote
1. I cannot get the Device page to display any info on my plug, it can "see" it but all the details are N/A. Does this work yet?
This could be tricky since the ESIA tries to intercept the uboot reboot countdown, you can try reset and click on the rescan button from the menu bar. I find the best way to close the ESIA , open a console and manage to stop the uboot countdown, then close the console application and open the ESIA .

You're right, it is a bit tricky. But eventually that was the method that worked for me.

Quote
Quote
5. If I just want to reload a new uboot.bin, where do I put it?  Do I need to build the complete "app" directory
structure?

Place the new uboot in the c:\Program Files\ESIA\uboot\uboot.bin directory (or the equivalent path in Linux based ESIA installation)

/usr/share/esia/uboot/uboot.bin on my Ubuntu machine. Thing is, I value having the choice of U-Boot version.

Documentation refers to http location under OS X. Doesn't have much to say about this location under linux. I found my apache error log reporting failures at http://127.0.0.1/AppStore/

So what I have so far is a number of subdirectories in http://127.0.0.1/AppStore/ , each of which contains a MANIFEST.cfg. Then, within http://127.0.0.1/AppStore/applications.list , each and every MANIFEST.cfg is concatenated. And the main esia panel shows data per the examples in the documentation.

I haven't tried any of the action buttons yet.
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #9 on: March 05, 2010, 11:50:13 PM »

Quote
Documentation refers to http location under OS X. Doesn't have much to say about this location under linux. I found my apache error log reporting failures at http://127.0.0.1/AppStore/

This feature is supported on every platform, so did you get the esia to show all applications on the web server?

You should have something like this:
/var/www/AppStore/applications +
                                             |
                                              - applications.list
                                              - Debian +
                                                          |
                                                           - rootfs.tar.gz
                                                           - MANIFEST.cfg
                                                           - modules.tar.gz
                                                           - uImage
The applications.list should include all "applications" concatenated MANIFEST.cfg.
Logged

marcus
Jr. Member
**

Karma: 5
Posts: 83


View Profile
« Reply #10 on: March 06, 2010, 01:40:33 AM »

Quote
Documentation refers to http location under OS X. Doesn't have much to say about this location under linux. I found my apache error log reporting failures at http://127.0.0.1/AppStore/

This feature is supported on every platform, so did you get the esia to show all applications on the web server?

You should have something like this:
/var/www/AppStore/applications +
                                             |
                                              - applications.list
                                              - Debian +
                                                          |
                                                           - rootfs.tar.gz
                                                           - MANIFEST.cfg
                                                           - modules.tar.gz
                                                           - uImage
The applications.list should include all "applications" concatenated MANIFEST.cfg.


Yes, thank you. This part is working fine. Just preparing to hit some buttons for the first time, now.
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #11 on: March 07, 2010, 12:33:50 PM »

Next drop will include configurable app store web server URL.
Logged

meldini@ngi.it
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #12 on: March 12, 2010, 06:56:33 AM »

hello, the installation fails at 15% with this message:

"Handle /mnt/usb/Debian/root.tar.gz"
"UBIFS: default file-system created"
"UBIFS: mounted UBI device 0, volume 0, name "rootfs""
"UBIFS: file system size:   515321856 bytes (503244 KiB, 491 MiB, 3994 LEBs)"
"UBIFS: journal size:       25804800 bytes (25200 KiB, 24 MiB, 200 LEBs)"
"UBIFS: media format:       w4/r0 (latest is w4/r0)"
"UBIFS: default compressor: lzo"
"UBIFS: reserved for root:  4952683 bytes (4836 KiB)"
"****** ERROR - no rootfs.tar.gz file found on USB stick"

anyone have any idea?
sorry for my english...
thanks!
Logged

meldini@ngi.it
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #13 on: March 16, 2010, 01:47:33 AM »

please...

 Cry
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #14 on: March 16, 2010, 02:09:17 AM »

does the rootfs tarball named root.tar.gz ?
This is the file that the esia looks for now.

I will check all distros on site and fix, the Debian squeeze is fine
Logged

Pages: [1] 2 3 ... 10
Print
Jump to: