Re: NeoTool

[Dale Maggee]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joop Boonen wrote:

> I've changed a few things in NeoTool.

Thanks for your contributions!

Please note however that I am working (*very* slowly!) on NeoTool v1.3,
and these changes may or may not appear in the new version. I am however
quite willing to consider this an 'official' v1.2.1.

> 1) No need to run it as root any more as long as you are in the uucp group.

NeoTool v1.3 has this, but it's achieved through a different method - It
prompts for your user password and then uses this to call 'sudo
dfu-util' rather than just 'dfu-util'. I will look into your mention of
the uucp group.

Also you should note that if you are concerned about security the temp
filenames should be generated using mktemp, i.e Line 48 would become:

tmp_error_log_path=`mktemp /tmp/neotool.XXX`


> 2) The config is saved in ~/.neotoolrc

NeoTool v1.3 will use ~/.neotool.conf to save user settings, and
/etc/neotool.conf to save root's settings, and/or to load defaults if no
user settings file is found (root's settings become the default). If
neither of these files is found, v1.3 will use /etc/frutil for backwards
compatibility. I will not be adding any support for ~/.neotoolrc, but I
may add a 'load custom settings' option which would allow you to specify
your own settings file. I would suggest that you should probably change
your v1.2.1 to use neotool.conf rather than neotoolrc for maximum
backwards compatibility.

> 3) The backup directory can be chosen, the default is: ~/openmoko/backups

For the record, this could already be achieved by adding a path to the
backup filename setting. NeoTool checks for the existence of the
specified path and attempts to create it if it cannot find it. This can
be used for example to store your backups in date-defined subfolders: if
you set your backup filename to: "/openmoko/backups/{date]/{image}",
NeoTool will automatically try to create a "17-Feb-2009" subfolder under
/data/openmoko, and will put the backup files in this folder. Please
ensure that your changes do not interfere with this.

> I couldn't reach the original maintainer yet. So i build version 1.2.1 for
> now, in the rpm packages.

I've been very busy over the last few months, hence my slow progress on
NeoTool, slow replies, and less involvement in this list. If you want to
have this considered an 'official' v1.2.1, please update the wiki page
for NeoTool at http://wiki.openmoko.org/wiki/NeoTool. :)

Regards
- -Dale

> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFJmhnsFbVnQRV3OEYRAqZbAJ0UBl69GBMxz3h+J9F3EVZKCj6GcQCglvMn
D+x7oHg3kijtAe1BUGLfiFs=
=udKM
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool (Correction!)

[Joop Boonen]

On Sun, February 15, 2009 2:35 pm, Joop Boonen wrote:
> All,
>
> I've changed a few things in NeoTool.
> 1) No need to run it as root any more as long as you are in the uucp
> group.
> 2) The config is saved in ~/.neotoolrc
> 3) The backup directory can be chosen, the default is: ~/openmoko/backups
>
> I couldn't reach the original maintainer yet. So i build version 1.2.1 for
> now, in the rpm packages.
>
> Regards,
>
> Joop Boonen.
>
> I couldn't reach the original maintainer yet.
>
> This is the NeoTool.patch:

I accedently added the wrong patch.

THis is the rioght one:

--- NeoTool-old 2009-02-14 21:07:33.0 +0100
+++ NeoTool 2009-02-15 14:38:51.0 +0100
@@ -1,5 +1,5 @@
 #!/bin/bash
-VERSION='1.2'
+VERSION='1.2.1'
 #
 # NeoTool $VERSION
 # By AntiSol, antisol (at) internode (dot) on (dot) net
@@ -41,12 +41,16 @@
 #  /data/openmoko/backups/{date}/{image}_backup
 #  and the {date} directory will be created by
NeoTool, assuming /data/openmoko/backups exists
 #  and you have permission.
+#  v1.2.1 - 15/02/2009 - joop_boonen (at) web (dot) de
+#  - Can now run as non root the user should be add to group
uucp
+#  - The config is now written in ~/.neotoolrc
+#  - The backup directory can now be choosen default
~/openmoko/backups
 #
 #

-settings_file='/etc/frutil'
+settings_file="$HOME/.neotoolrc"
 tmp_error_log_path='/tmp/flash-error-log'
-tmpfile='/tmp/frutil.tmp'
+tmpfile='/tmp/neotool.tmp'

 function find_dfu {
#use 'which'...
@@ -75,7 +79,7 @@
clear
echo 'Downloading dfu-util...'
rm ./dfu-util > /dev/null 2>&1
-   wget
http://downloads.openmoko.org/daily/dfu-util
+   wget
http://downloads.openmoko.org/distro/releases/Om2008.9/dfu-util
chmod a+x ./dfu-util >/dev/null
dfutils_path='./dfu-util'
else
@@ -185,8 +189,8 @@

 function flash {

-   if [ "$user" != root ]; then
-   zenity --error --text "You can only flash your device if
you are root!"
+   if [ "$groups" = "${groups/uucp/}" ]; then
+   zenity --error --text "You can only flash your device if
you are in the uucp group!"
return
fi

@@ -318,7 +322,7 @@
 }

 function setup_menu {
-   sans=`zenity --title "NeoTool Configurification" --text "Choose an
option" --list --height=320 --width=500  --column "" --column "" 1 "Locate
dfu-util ($dfutils_path)" 2 "Set your device's IP ($FRIP)" 3 "Choose
backup filename ($backupfn)" 4 "Setup date command ($datecmd)" 5 "Test
settings defined in (3) and (4)" 6 "Save These Settings" 7 "Reset to
defaults" 8 "Back to Main Menu"`
+   sans=`zenity --title "NeoTool Configurification" --text "Choose an
option" --list --height=320 --width=500  --column "" --column "" 1 "Locate
dfu-util ($dfutils_path)" 2 "Set your device's IP ($FRIP)" 3 "Choose
backup filename ($backupfn)" 4 "Setup date command ($datecmd)" 5 "Choose
backup directory ($backupdir)" 6 "Test settings defined in (3), (4) and
(5)" 7 "Save These Settings" 8 "Reset to defaults" 9 "Back to Main Menu"`
 }


@@ -355,29 +359,31 @@
fi
;;
5)
-   tmp=${backupfn//"{date}"/"`$datecmd`"}
+   oldbackupdir="$backupdir"
+   backupdir=$(zenity --entry --text "`printf "Enter
the default directoryname to be used for backups.\nuse '{image}' for the
Image type (kernel, rootfs, etc), \nand '{date}' for the date.\n the file
extension will be added automatically."`" --entry-text "$backupdir"
--title "Configure Backup Directoryname")
+   if [ -z "$backupdir" ]; then
+   backupdir=$oldbackupdir
+   fi
+   ;;
+   6)
+   tmp=$backupdir"/"${backupfn//"{date}"/"`$datecmd`"}

tmp=${tmp//"{image}"/"rootfs"}".jffs2\n"${tmp//"{image}"/"kern

NeoTool

[Joop Boonen]

All,

I've changed a few things in NeoTool.
1) No need to run it as root any more as long as you are in the uucp group.
2) The config is saved in ~/.neotoolrc
3) The backup directory can be chosen, the default is: ~/openmoko/backups

I couldn't reach the original maintainer yet. So i build version 1.2.1 for
now, in the rpm packages.

Regards,

Joop Boonen.

I couldn't reach the original maintainer yet.

This is the NeoTool.patch:

--- NeoTool-old 2009-02-14 21:07:33.0 +0100
+++ NeoTool 2009-02-15 13:59:36.0 +0100
@@ -1,5 +1,5 @@
 #!/bin/bash
-VERSION='1.2'
+VERSION='1.2.1'
 #####
 # NeoTool $VERSION
 # By AntiSol, antisol (at) internode (dot) on (dot) net
@@ -41,12 +41,16 @@
 #  /data/openmoko/backups/{date}/{image}_backup
 #  and the {date} directory will be created by
NeoTool, assuming /data/openmoko/backups exists
 #  and you have permission.
+#  v1.2.1 - 15/02/2009 - joop_boonen (at) web (dot) de
+#  - Can now run as non root the user should be add to group
uucp
+#  - The config is now written in ~/.neotoolrc
+#  - The backup directory can now be choosen default
~/openmoko/backups
 #
 #

-settings_file='/etc/frutil'
+settings_file="$HOME/.neotoolrc"
 tmp_error_log_path='/tmp/flash-error-log'
-tmpfile='/tmp/frutil.tmp'
+tmpfile='/tmp/neotool.tmp'

 function find_dfu {
#use 'which'...
@@ -75,7 +79,7 @@
clear
echo 'Downloading dfu-util...'
rm ./dfu-util > /dev/null 2>&1
-   wget
http://downloads.openmoko.org/daily/dfu-util
+   wget
http://downloads.openmoko.org/distro/releases/Om2008.9/dfu-util
chmod a+x ./dfu-util >/dev/null
dfutils_path='./dfu-util'
else
@@ -185,8 +189,8 @@

 function flash {

-   if [ "$user" != root ]; then
-   zenity --error --text "You can only flash your device if
you are root!"
+   if [ "$group" != uucp ]; then
+   zenity --error --text "You can only flash your device if
you are root! $group"
return
fi

@@ -318,7 +322,7 @@
 }

 function setup_menu {
-   sans=`zenity --title "NeoTool Configurification" --text "Choose an
option" --list --height=320 --width=500  --column "" --column "" 1 "Locate
dfu-util ($dfutils_path)" 2 "Set your device's IP ($FRIP)" 3 "Choose
backup filename ($backupfn)" 4 "Setup date command ($datecmd)" 5 "Test
settings defined in (3) and (4)" 6 "Save These Settings" 7 "Reset to
defaults" 8 "Back to Main Menu"`
+   sans=`zenity --title "NeoTool Configurification" --text "Choose an
option" --list --height=320 --width=500  --column "" --column "" 1 "Locate
dfu-util ($dfutils_path)" 2 "Set your device's IP ($FRIP)" 3 "Choose
backup filename ($backupfn)" 4 "Setup date command ($datecmd)" 5 "Choose
backup directory ($backupdir)" 6 "Test settings defined in (3), (4) and
(5)" 7 "Save These Settings" 8 "Reset to defaults" 9 "Back to Main Menu"`
 }


@@ -355,29 +359,31 @@
fi
;;
5)
-   tmp=${backupfn//"{date}"/"`$datecmd`"}
+   oldbackupdir="$backupdir"
+   backupdir=$(zenity --entry --text "`printf "Enter
the default directoryname to be used for backups.\nuse '{image}' for the
Image type (kernel, rootfs, etc), \nand '{date}' for the date.\n the file
extension will be added automatically."`" --entry-text "$backupdir"
--title "Configure Backup Directoryname")
+   if [ -z "$backupdir" ]; then
+   backupdir=$oldbackupdir
+   fi
+   ;;
+   6)
+   tmp=$backupdir"/"${backupfn//"{date}"/"`$datecmd`"}

tmp=${tmp//"{image}"/"rootfs"}".jffs2\n"${tmp//"{image}"/"kernel"}".bin"
zenity --info --title "Example Backup File" --text
"Using the rules defined by current settings,
backup filenames will look something like
this:\n\n$tmp"
   

RPM packages for dfu-util and NeoTool

[Joop Boonen]

All,

I've created rpm packages for dfu-util and NeoTool.
You can find the links on the web pages for these tools:
http://wiki.openmoko.org/wiki/Dfu-util
http://wiki.openmoko.org/wiki/NeoTool

dfu-util will be updated to a more recent svn version on a regular bases.

Regards,

Joop.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool/dfu-util bug - No such Alternate Setting: "rootfs"

[abatrour]

The same things happens to me, I just run it again and it works..
-- 
View this message in context: 
http://n2.nabble.com/NeoTool-dfu-util-bug---No-such-Alternate-Setting%3A-%22rootfs%22-tp1465274p1468069.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool/dfu-util bug - No such Alternate Setting: "rootfs"

[Dale Maggee]

Mikko Ohtamaa wrote:
> Symptoms dfu-util/Neotool fails to flash Openmoko when using wiki.openmoko.org
> instructions:
>
> sudo ./dfu-util.1 -a rootfs -R -D 
> Fat_and_Dirty_OM.200809_20081023.rootfs.jffs2 
> dfu-util - (C) 2007 by OpenMoko Inc.
> This program is Free Software and has ABSOLUTELY NO WARRANTY
>
> Opening USB Device 0x:0x...
> Claiming USB DFU Runtime Interface...
> Determining device status: state = dfuIDLE, status = 0
> WARNING: Runtime device already in DFU state ?!?
> No such Alternate Setting: "rootfs"
>
> Cause: 
>
> Neotool/dfu-util automatically picks wrong USB device - it must pick this one 
>
> Found DFU Runtime: [0x1457:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="USB
> Device Firmware Upgrade"
>
> In my case, the wrong device was something built into my laptop:
>
> Bus 005 Device 003: ID 03f0:181d Hewlett-Packard 
>
> Workaround:
>
> Use dfu-util -d parameter to specify device id manually.
>
>
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool/dfu-util bug - No such Alternate Setting: "rootfs"

[Dale Maggee]

Hi,

Are you using the latest version of NeoTool? v1.1 and up should be able 
to detect and handle this situation by presenting you with a screen 
asking you which dfu-capable device you want to flash.

If you are using the latest version, please run 'dfu-util -l' and post 
the output here.

Regards,
-Dale

Mikko Ohtamaa wrote:
> Symptoms dfu-util/Neotool fails to flash Openmoko when using wiki.openmoko.org
> instructions:
>
> sudo ./dfu-util.1 -a rootfs -R -D 
> Fat_and_Dirty_OM.200809_20081023.rootfs.jffs2 
> dfu-util - (C) 2007 by OpenMoko Inc.
> This program is Free Software and has ABSOLUTELY NO WARRANTY
>
> Opening USB Device 0x:0x...
> Claiming USB DFU Runtime Interface...
> Determining device status: state = dfuIDLE, status = 0
> WARNING: Runtime device already in DFU state ?!?
> No such Alternate Setting: "rootfs"
>
> Cause: 
>
> Neotool/dfu-util automatically picks wrong USB device - it must pick this one 
>
> Found DFU Runtime: [0x1457:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="USB
> Device Firmware Upgrade"
>
> In my case, the wrong device was something built into my laptop:
>
> Bus 005 Device 003: ID 03f0:181d Hewlett-Packard 
>
> Workaround:
>
> Use dfu-util -d parameter to specify device id manually.
>
>
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

NeoTool/dfu-util bug - No such Alternate Setting: "rootfs"

[Mikko Ohtamaa]

Symptoms dfu-util/Neotool fails to flash Openmoko when using wiki.openmoko.org
instructions:

sudo ./dfu-util.1 -a rootfs -R -D Fat_and_Dirty_OM.200809_20081023.rootfs.jffs2 
dfu-util - (C) 2007 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x:0x...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
No such Alternate Setting: "rootfs"

Cause: 

Neotool/dfu-util automatically picks wrong USB device - it must pick this one 

Found DFU Runtime: [0x1457:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="USB
Device Firmware Upgrade"

In my case, the wrong device was something built into my laptop:

Bus 005 Device 003: ID 03f0:181d Hewlett-Packard 

Workaround:

Use dfu-util -d parameter to specify device id manually.




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Pander]

Robin Paulson wrote:
> 2008/11/2 Dale Maggee <[EMAIL PROTECTED]>:
>> It's not impossible because of the pause while downloading, I'd just
>> make NeoTool download the file before showing the "About to flash,
>> Please boot to the menu" message.
> 
> ok, that should work
> 
>> One problem I had was determining where to get the files, and how to
>> tell when there's a new release - I'd rather not hard code addresses
>> into it, so for this to work there would need to be something like:
>>
>> http://downloads.openmoko.com/releases/latest/release.jffs2
>> http://downloads.openmoko.com/releases/latest/kernel.bin
>>
>> you say "there is a link on the om site pointing to the 'latest'
>> kernel/uboot/rootfs to download"... which link are you referring to?

One should also consider offering FDOM and QtExtended, not only the OM
release.

> 
> http://downloads.openmoko.org/releases/Om2008.9/Om2008.9.rootfs.jffs2
> which has the same date stamp and size as the newest file
> 
> and so on
> 
>> Another issue I had was determining which files to download: I'd need to
>> prompt to find out whether to get the GTA01 or GTA02 files.
> 
> i'm sure this can be found from the command-line, and hence a bash
> script by ssh'ing into the phone before re-booting. or use a button to
> do it manually, if the user doesn't want to do that
> 
> 
>> Alternatively, I guess it would be possible to traverse
>> downloads.openmoko.org and present a menu allowing the user to specify
>> what to download, but I don't know how to at the moment, and this is
>> basically duplicating the functionality of pointing your browser to this
>> address, so it seems kind of redundant to me.
> 
> still a bit clumsy - humans are so good at making mistakes; i'm
> paranoid about flashing the wrong thing and screwing my phone.
> 
> at worst, you could parse the contents of the html, find the latest
> release by some text manipulation and go from there. assuming om don't
> change the layout and structure
> but yes, this is probably no small work, and as you say, is
> duplicating the browser
> 
>> In the end I decided not to do it because I figured I'd basically be
>> duplicating your browser's functionality, and that I would be better off
>> devoting my efforts to more Neo-specific stuff, like adding the ability
>> to backup.
> 
> sure. each has their own ideas. maybe i'm going over the top, and it's
> simple enough already?
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Pander]

Robin Paulson wrote:
> 2008/10/31 Dale Maggee <[EMAIL PROTECTED]>:
>> Just a quick note to announce a new version of NeoTool.
>>
> 
> nice work!
> 
> could i make a feature request? as there is a link on the om site
> pointing to the 'latest' kernel/uboot/rootfs to download, could
> neotool be developed further, to download it and then flash it all in
> one step?

U-Boot will be replaced in the near futuru with Qi, perhaps with this in
mind, also provide this functionality for Qi.

Maybe some flash repositories could be set up offering sets or
combinations of http://wiki.openmoko.org/wiki/Distributions#Images
However, the download sites offering the images are all very different
in how they offer it, with what naming convention etc.

This would be of great advantage for normal users. Power users can
download and do all that themselves.

> 
> or is this impossible because a long pause (while the file's being
> downloaded) at the uboot screen will cause the neo to carry on
> booting? or is there a way round this, i.e. telling the neo to wait
> for an indefinite amount of time, or tricking it into thinking
> something is happening while the file downloads?

I'd suggest first download all, then connect and write the images.

> 
> thanks
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Pander]

Dale Maggee wrote:
>> Thanks for Neotool!
>>   
> You're welcome! :)
> 
>> Found a typo: Neotool Configurification (instead of Configuration)
>> And menu item 'setup neotool' takes to 'neotool configuration', a
>> consistency in the names would make it easier to use.
>>   
> Are you sure that it's inconsistent? I just had a look and I don't see 
> "configuration" anywhere, I believe it's pretty consistently called 
> "configurification". Are you using the new v1.2? It could be that I had 
> "configuration" in there somewhere, spotted and changed it, but didn't 
> include it in the changelog. This is not a typo, it's a word I invented 
> ages back and quite like... ;)
> 
>> Could you add 'backup home folder' option there as well, maybe even
>> 'Backup µSD card'? I know it's slow but some users might find it
>> useful to backup some scripts they've created. I might also have
>> understood this wrong that backing up rootfs does this (but the files
>> are not easily accessible?)
>>   
> "Backup home" Is actually already on my todo list, as it's something 
> I've wanted to do, so yes, I definitely will add that, once I get the 
> time. Backup MicroSD is a great suggestion, too, I'll put it on the todo 
> list as well.

How about offering this functionality: backup home as to microSD?
(Possibly as home-'datetime'.tar.gz)

>> I also noticed that (Kubuntu intrepid, kde4) for some reason always
>> when I click a button on NeoTool the new view is opened behind another
>> open window.
>>   
> That's odd, and to be honest I have absolutely no idea why it's 
> happening - I'd guess that it's an issue with either zenity or kde4, or 
> a combination of both, but I really don't know about that one! All I can 
> really say is "that's not supposed to be happening" and "it doesn't do 
> that for me!" (Fedora, gnome). Anybody who has a suggestion is welcome 
> to add their $0.02!

Please, add it as a comment on https://bugs.launchpad.net/ubuntu/+bug/288747

> 
>> Great tool, thanks!
>>   
> 
> Ooooh, praise! You're very welcome! :)
> 
> -Dale
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Risto H. Kurppa]

On Sat, Nov 1, 2008 at 3:54 PM, Dale Maggee <[EMAIL PROTECTED]> wrote:
>> Found a typo: Neotool Configurification (instead of Configuration)
>> And menu item 'setup neotool' takes to 'neotool configuration', a
>> consistency in the names would make it easier to use.
>>
> Are you sure that it's inconsistent? I just had a look and I don't see
> "configuration" anywhere, I believe it's pretty consistently called
> "configurification". Are you using the new v1.2? It could be that I had
> "configuration" in there somewhere, spotted and changed it, but didn't
> include it in the changelog. This is not a typo, it's a word I invented
> ages back and quite like... ;)

oh, okay.. I hope other developers don't start doing the same..
Firefoxingbling Brohmser

But anyway: the menu says 'setup' but the window that opens is
'configurification'.

thanks!

r



-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Robin Paulson]

2008/11/2 Dale Maggee <[EMAIL PROTECTED]>:
> It's not impossible because of the pause while downloading, I'd just
> make NeoTool download the file before showing the "About to flash,
> Please boot to the menu" message.

ok, that should work

> One problem I had was determining where to get the files, and how to
> tell when there's a new release - I'd rather not hard code addresses
> into it, so for this to work there would need to be something like:
>
> http://downloads.openmoko.com/releases/latest/release.jffs2
> http://downloads.openmoko.com/releases/latest/kernel.bin
>
> you say "there is a link on the om site pointing to the 'latest'
> kernel/uboot/rootfs to download"... which link are you referring to?

http://downloads.openmoko.org/releases/Om2008.9/Om2008.9.rootfs.jffs2
which has the same date stamp and size as the newest file

and so on

> Another issue I had was determining which files to download: I'd need to
> prompt to find out whether to get the GTA01 or GTA02 files.

i'm sure this can be found from the command-line, and hence a bash
script by ssh'ing into the phone before re-booting. or use a button to
do it manually, if the user doesn't want to do that


> Alternatively, I guess it would be possible to traverse
> downloads.openmoko.org and present a menu allowing the user to specify
> what to download, but I don't know how to at the moment, and this is
> basically duplicating the functionality of pointing your browser to this
> address, so it seems kind of redundant to me.

still a bit clumsy - humans are so good at making mistakes; i'm
paranoid about flashing the wrong thing and screwing my phone.

at worst, you could parse the contents of the html, find the latest
release by some text manipulation and go from there. assuming om don't
change the layout and structure
but yes, this is probably no small work, and as you say, is
duplicating the browser

> In the end I decided not to do it because I figured I'd basically be
> duplicating your browser's functionality, and that I would be better off
> devoting my efforts to more Neo-specific stuff, like adding the ability
> to backup.

sure. each has their own ideas. maybe i'm going over the top, and it's
simple enough already?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Dale Maggee]

> nice work!
>   

Thanks
> could i make a feature request? as there is a link on the om site
> pointing to the 'latest' kernel/uboot/rootfs to download, could
> neotool be developed further, to download it and then flash it all in
> one step?
>
> or is this impossible because a long pause (while the file's being
> downloaded) at the uboot screen will cause the neo to carry on
> booting? or is there a way round this, i.e. telling the neo to wait
> for an indefinite amount of time, or tricking it into thinking
> something is happening while the file downloads?
>   
I've had this thought, too - it has occurred to me that a 'download 
latest release' option would be cool...

It's not impossible because of the pause while downloading, I'd just 
make NeoTool download the file before showing the "About to flash, 
Please boot to the menu" message.

There are a few problems, though:

One problem I had was determining where to get the files, and how to 
tell when there's a new release - I'd rather not hard code addresses 
into it, so for this to work there would need to be something like:

http://downloads.openmoko.com/releases/latest/release.jffs2
http://downloads.openmoko.com/releases/latest/kernel.bin

you say "there is a link on the om site pointing to the 'latest' 
kernel/uboot/rootfs to download"... which link are you referring to?

Another issue I had was determining which files to download: I'd need to 
prompt to find out whether to get the GTA01 or GTA02 files.

Alternatively, I guess it would be possible to traverse 
downloads.openmoko.org and present a menu allowing the user to specify 
what to download, but I don't know how to at the moment, and this is 
basically duplicating the functionality of pointing your browser to this 
address, so it seems kind of redundant to me.

In the end I decided not to do it because I figured I'd basically be 
duplicating your browser's functionality, and that I would be better off 
devoting my efforts to more Neo-specific stuff, like adding the ability 
to backup.

If anybody has any other Ideas on how I might go about implementing 
this, I'd love to hear them.

-Dale

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Robin Paulson]

2008/10/31 Dale Maggee <[EMAIL PROTECTED]>:
> Just a quick note to announce a new version of NeoTool.
>

nice work!

could i make a feature request? as there is a link on the om site
pointing to the 'latest' kernel/uboot/rootfs to download, could
neotool be developed further, to download it and then flash it all in
one step?

or is this impossible because a long pause (while the file's being
downloaded) at the uboot screen will cause the neo to carry on
booting? or is there a way round this, i.e. telling the neo to wait
for an indefinite amount of time, or tricking it into thinking
something is happening while the file downloads?

thanks

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Dale Maggee]

> Thanks for Neotool!
>   
You're welcome! :)

> Found a typo: Neotool Configurification (instead of Configuration)
> And menu item 'setup neotool' takes to 'neotool configuration', a
> consistency in the names would make it easier to use.
>   
Are you sure that it's inconsistent? I just had a look and I don't see 
"configuration" anywhere, I believe it's pretty consistently called 
"configurification". Are you using the new v1.2? It could be that I had 
"configuration" in there somewhere, spotted and changed it, but didn't 
include it in the changelog. This is not a typo, it's a word I invented 
ages back and quite like... ;)

> Could you add 'backup home folder' option there as well, maybe even
> 'Backup µSD card'? I know it's slow but some users might find it
> useful to backup some scripts they've created. I might also have
> understood this wrong that backing up rootfs does this (but the files
> are not easily accessible?)
>   
"Backup home" Is actually already on my todo list, as it's something 
I've wanted to do, so yes, I definitely will add that, once I get the 
time. Backup MicroSD is a great suggestion, too, I'll put it on the todo 
list as well.

> I also noticed that (Kubuntu intrepid, kde4) for some reason always
> when I click a button on NeoTool the new view is opened behind another
> open window.
>   
That's odd, and to be honest I have absolutely no idea why it's 
happening - I'd guess that it's an issue with either zenity or kde4, or 
a combination of both, but I really don't know about that one! All I can 
really say is "that's not supposed to be happening" and "it doesn't do 
that for me!" (Fedora, gnome). Anybody who has a suggestion is welcome 
to add their $0.02!

>
> Great tool, thanks!
>   

Ooooh, praise! You're very welcome! :)

-Dale

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Risto H. Kurppa]

Thanks for Neotool!

Found a typo: Neotool Configurification (instead of Configuration)
And menu item 'setup neotool' takes to 'neotool configuration', a
consistency in the names would make it easier to use.

Could you add 'backup home folder' option there as well, maybe even
'Backup µSD card'? I know it's slow but some users might find it
useful to backup some scripts they've created. I might also have
understood this wrong that backing up rootfs does this (but the files
are not easily accessible?)

I also noticed that (Kubuntu intrepid, kde4) for some reason always
when I click a button on NeoTool the new view is opened behind another
open window.


Great tool, thanks!

-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [Fwd: [Bug 288747] Re: [needs-packaging] neotool]

[Dale Maggee]

Wow, cool! Does this mean that there's now a debian package?

I just saw your other message about this, does this mean that the issues 
you were having are solved?

Great stuff.

It would be great if you could update the NeoTool wiki page with 
instructions on installing on debian / ubuntu. I don't run debian or 
ubuntu, so don't know much about their packaging systems...

Regards,
-Dale


Pander wrote:
> NeoTool package for Ubuntu
>   
>
> 
>
> Subject:
> [Bug 288747] Re: [needs-packaging] neotool
> From:
> Heikki Mäntysaari <[EMAIL PROTECTED]>
> Date:
> Fri, 31 Oct 2008 20:35:09 -
> To:
> [EMAIL PROTECTED]
>
> To:
> [EMAIL PROTECTED]
>
>
> I made a package for Debian and uploaded it to mentors.debian.net, see
> http://mentors.debian.net/cgi-bin/sponsor-
> pkglist?action=details;package=neotool
>
> Debian bug report: http://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=504131
>
> ** Changed in: ubuntu
>  Assignee: (unassigned) => Heikki Mäntysaari (heikki-mantysaari)
>Status: New => In Progress
>
> ** Also affects: debian via
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504131
>Importance: Unknown
>Status: Unknown
>
>   
> 
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[Fwd: [Bug 288747] Re: [needs-packaging] neotool]

[Pander]

NeoTool package for Ubuntu
--- Begin Message ---
I made a package for Debian and uploaded it to mentors.debian.net, see
http://mentors.debian.net/cgi-bin/sponsor-
pkglist?action=details;package=neotool

Debian bug report: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=504131

** Changed in: ubuntu
 Assignee: (unassigned) => Heikki Mäntysaari (heikki-mantysaari)
   Status: New => In Progress

** Also affects: debian via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504131
   Importance: Unknown
   Status: Unknown

-- 
[needs-packaging] neotool
https://bugs.launchpad.net/bugs/288747
You received this bug notification because you are a direct subscriber
of the bug.
--- End Message ---
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool - v1.2 available

[Pander]

Hi all,

Dale, thanks for the new version.

Here is the Ubuntu package request for NeoTool
  https://bugs.launchpad.net/ubuntu/+bug/288747

And almost off topic, request to Ubuntu to semi automatically setup USB
networking and mount partitions of an OpenMoko device
  https://bugs.launchpad.net/ubuntu/+bug/289548

The latter has stranded a bit but I'm sure that, in combination with
NeoTool expertise, something like this can be developed. Any ideas how
to continue on this?

Regards,

Pander

Dale Maggee wrote:
> All,
> 
> Just a quick note to announce a new version of NeoTool.
> 
> Life has interfered with my ability to work on this lately, so there are 
> only a couple of smallish changes:
> 
> - Changed information at pre-flash prompt to include instructions for 
> how to get to the NOR menu.
> eliminated any mention of NAND, as everything can be flashed from NOR.
> 
> - bugfix - when user selects a filename under 'customize backup 
> filenames' and then presses cancel,
> the selected filename was set to nothing.
> 
> - NeoTool now checks that the path of backup files exist, and attempts 
> to create it if it doesn't.
> This allows you to organise your backups in a folder hierarchy, i.e 
> set the backup filename to:
> /data/openmoko/backups/{date}/{image}_backup
> and the {date} directory will be created by NeoTool, assuming 
> /data/openmoko/backups exists
> and you have permission.
> 
> Info / Download link:
> http://wiki.openmoko.org/wiki/NeoTool
> 
> Enjoy,
> -Dale
> 
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

NeoTool - v1.2 available

[Dale Maggee]

All,

Just a quick note to announce a new version of NeoTool.

Life has interfered with my ability to work on this lately, so there are 
only a couple of smallish changes:

- Changed information at pre-flash prompt to include instructions for 
how to get to the NOR menu.
eliminated any mention of NAND, as everything can be flashed from NOR.

- bugfix - when user selects a filename under 'customize backup 
filenames' and then presses cancel,
the selected filename was set to nothing.

- NeoTool now checks that the path of backup files exist, and attempts 
to create it if it doesn't.
This allows you to organise your backups in a folder hierarchy, i.e 
set the backup filename to:
/data/openmoko/backups/{date}/{image}_backup
and the {date} directory will be created by NeoTool, assuming 
/data/openmoko/backups exists
and you have permission.

Info / Download link:
http://wiki.openmoko.org/wiki/NeoTool

Enjoy,
-Dale

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Dale Maggee]

The rootfs is not backed up using dfu-util. It produces a flashable 
image which works fine.

I have tested the dfu-upload stuff, but I have not attempted to flash my 
phone with the files I get from this, so I can't comment

Neotool relies on dfu-util - if dfu-util is broken, neotool will produce 
dodgy images.

When I use neotool to backup, I backup the rootfs and the kernel via the 
scp method. This works fine and produces flashable images - I've tested 
this by flashing both rootfs and kernel numerous times.

Regards
-Dale

Shawn "prjktdtnt" Thompson wrote:
> Tomasz Melcer wrote:
>   
>> On 2008-09-17, Dale Maggee wrote:
>>   
>> 
>>> - Backup has been radically enhanced, and now supports configurable 
>>> backup filenames, as well as the ability to backup everything via a 
>>> combination of the mkfs-jffs2 and dfu -U methods.
>>> 
>>>   
>> Does the dfu upload work for you? I tried to do some uploads, but either
>> dfu-util returned an error, or even if it didn't, the backup was
>> unusable --- there were filesystem errors after flashing FR with them.
>>
>> Tomasz Melcer
>>
>>
>> ___
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
>>   
>> 
> Tomasz,
> From what I remember reading, somewhere in the wiki, that dfu-util 
> has a bug in the upload feature currently that causes that.
>
> -Shawn
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Shawn "prjktdtnt" Thompson]

Tomasz Melcer wrote:
> On 2008-09-17, Dale Maggee wrote:
>   
>> - Backup has been radically enhanced, and now supports configurable 
>> backup filenames, as well as the ability to backup everything via a 
>> combination of the mkfs-jffs2 and dfu -U methods.
>> 
> Does the dfu upload work for you? I tried to do some uploads, but either
> dfu-util returned an error, or even if it didn't, the backup was
> unusable --- there were filesystem errors after flashing FR with them.
>
> Tomasz Melcer
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>   
Tomasz,
From what I remember reading, somewhere in the wiki, that dfu-util 
has a bug in the upload feature currently that causes that.

-Shawn

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Tomasz Melcer]

On 2008-09-17, Dale Maggee wrote:
> - Backup has been radically enhanced, and now supports configurable 
> backup filenames, as well as the ability to backup everything via a 
> combination of the mkfs-jffs2 and dfu -U methods.
Does the dfu upload work for you? I tried to do some uploads, but either
dfu-util returned an error, or even if it didn't, the backup was
unusable --- there were filesystem errors after flashing FR with them.

Tomasz Melcer


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available [OT]

[Dale Maggee]

[EMAIL PROTECTED] wrote:
> Dale Maggee wrote:
>   
>> [1] http://users.on.net/~antisol/neotool
>> [2] http://wiki.openmoko.org/wiki/NeoTool
>>   
>> 
>
>
> Oh ... you're antisol :)
>
> I'm roguetr, nice to see you friend ;)
>
> hehe
>
> Sarton
>   
I am indeed. ;)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Dale Maggee]

Shawn "prjktdtnt" Thompson wrote:
>
> Dale,
> This is some great work! Thank you for letting me work with you on 
> this to support multiple devices.
> -Shawn
>   
Thanks! And thanks for your help and suggestion!

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Dale Maggee]

Daniel Hedblom wrote:
> Looks really nice and seems friendly enough for the beginners. Its
> amazing what one can do with bash =)
>
> //danielh
>   
Thanks! :)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available [OT]

[roguemoko]

Dale Maggee wrote:
> [1] http://users.on.net/~antisol/neotool
> [2] http://wiki.openmoko.org/wiki/NeoTool
>   


Oh ... you're antisol :)

I'm roguetr, nice to see you friend ;)

hehe

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Shawn "prjktdtnt" Thompson]

Dale Maggee wrote:
> I've been hard at work again, and a new version my utility is now 
> available...
>
> I've renamed it (again) to NeoTool.
>
> Download it from [1]
>
> I've also created a wiki page for it at [2], and linked to it from the 
> Flash and Backup wiki pages.
>
> Major new features include:
> - Support for multiple DFU-capable devices - you'll see a menu asking 
> you to choose which device if you have more than one attached
>
> - Backup has been radically enhanced, and now supports configurable 
> backup filenames, as well as the ability to backup everything via a 
> combination of the mkfs-jffs2 and dfu -U methods.
>
> There are also other improvements and changes which are documented on 
> the wiki page.
>
> [1] http://users.on.net/~antisol/neotool
> [2] http://wiki.openmoko.org/wiki/NeoTool
>
> enjoy!
>
> -Dale
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>   
Dale,
This is some great work! Thank you for letting me work with you on 
this to support multiple devices.
-Shawn

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: NeoTool v1.1 is available

[Daniel Hedblom]

Looks really nice and seems friendly enough for the beginners. Its
amazing what one can do with bash =)

//danielh

2008/9/17 Dale Maggee <[EMAIL PROTECTED]>:
> I've been hard at work again, and a new version my utility is now
> available...
>
> I've renamed it (again) to NeoTool.
>
> Download it from [1]
>
> I've also created a wiki page for it at [2], and linked to it from the
> Flash and Backup wiki pages.
>
> Major new features include:
> - Support for multiple DFU-capable devices - you'll see a menu asking
> you to choose which device if you have more than one attached
>
> - Backup has been radically enhanced, and now supports configurable
> backup filenames, as well as the ability to backup everything via a
> combination of the mkfs-jffs2 and dfu -U methods.
>
> There are also other improvements and changes which are documented on
> the wiki page.
>
> [1] http://users.on.net/~antisol/neotool
> [2] http://wiki.openmoko.org/wiki/NeoTool
>
> enjoy!
>
> -Dale
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

NeoTool v1.1 is available

[Dale Maggee]

I've been hard at work again, and a new version my utility is now 
available...

I've renamed it (again) to NeoTool.

Download it from [1]

I've also created a wiki page for it at [2], and linked to it from the 
Flash and Backup wiki pages.

Major new features include:
- Support for multiple DFU-capable devices - you'll see a menu asking 
you to choose which device if you have more than one attached

- Backup has been radically enhanced, and now supports configurable 
backup filenames, as well as the ability to backup everything via a 
combination of the mkfs-jffs2 and dfu -U methods.

There are also other improvements and changes which are documented on 
the wiki page.

[1] http://users.on.net/~antisol/neotool
[2] http://wiki.openmoko.org/wiki/NeoTool

enjoy!

-Dale

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community