rkflashtool-devel — Development discussion

Re: [Rkflashtool-devel] Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows

[Ivo v. P. <iv...@gm...>]

Hi,

Thanks for your feedback. I'm currently in the process of releasing
v6.0 and cross-builds for win32/win64 with the latest libusb. This
might fix your problem, too. If not, we'll have to investigate further.

I was sort of hoping you had an asmedia usb controller, as that
has been mentioned before on other projects as the cause of similar
problems, but that's not the case. Anyway, as I'm adding Mac OS X cross
builds to the project, too, and cleaning up a few things, it might take
a few more days to sort things out, but there's a v6 release coming
soon, including binary builds and a bunch of new features contributed by
others.

Regards,
Ivo

On Wed, 12 Oct 2016 15:31:35 +0200 "Ing. Federico Rampin"
<fed...@gm...> wrote:
> Dear,
>   here's the output for lspci | grep -i usb:
> 
> 
> 
> *00:14.0 USB controller: Intel Corporation 7 Series/C210 Series
> Chipset Family USB xHCI Host Controller (rev 04)00:1a.0 USB
> controller: Intel Corporation 7 Series/C210 Series Chipset Family USB
> Enhanced Host Controller #2 (rev 04)00:1d.0 USB controller: Intel
> Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host
> Controller #1 (rev 04)*
> 
> 
> Thanks a lot.
> 
> 
> 2016-10-08 20:36 GMT+02:00 Ing. Federico Rampin
> <fed...@gm...>:
> 
> > Dear,
> >   I'll follow your suggestions Windows side.
> >
> > No USB hub is involved.
> >
> > I've been trying in 2 computers, the 1st returns the quoted output,
> > the second only a "rkflashtool: fatal: cannot open device".
> >
> > The strangeness is test al other flashing tools are working, so
> > sounds not to be a hardware/drivers issue, correct?
> >
> > I'll do lspci | grep -i usb under Ubuntu and feedback.
> >
> > Thanks a lot for support.
> >
> > Il 08 Ott 2016 8:22 PM, "Ivo van Poorten" <iv...@gm...> ha
> > scritto:
> >
> >> Hi,
> >>
> >> On Thu, 6 Oct 2016 17:25:04 +0200 "Ing. Federico Rampin"
> >> <fed...@gm...> wrote:
> >> > Dears,
> >> > I'm trying to do a full NAND backup on Windows with rkflashtool
> >> > 5.1 (I can succeed on Ubuntu, but on Windows I have several
> >> > errors).
> >> >
> >> >[snip...]
> >> >
> >> > *C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto
> >> > ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin
> >> > rkflashtool: info: rkflashtool v5.1 libusb: 0.000000 warning
> >> > [init_device] could not get node connection information for
> >> > device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87]
> >> > Parametro non corretto. libusb: 0.000000 error [init_device]
> >> > device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is
> >> > no longer connected! libusb: 0.015627 error [init_device] device
> >> > '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> >> > connected! libusb: 0.062504 warning [init_device] could not get
> >> > node connection information for device
> >>
> >> Looks like your (on board?) USB hub is not supplying the correct
> >> node information. Are you connecting the device directly to your
> >> motherboard or do you use an external hub in between?
> >>
> >> You could try updating the drivers for your on board USB and/or
> >> external hub to the latest version and see if that works. Or
> >> perhaps use an external hub if you are currently not, or the other
> >> way around.
> >>
> >> If none of the above works, could you run:
> >>
> >> lspci | grep -i usb
> >>
> >> under Ubuntu?
> >>
> >> Regards,
> >> Ivo
> >>
> >>

Re: [Rkflashtool-devel] Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows

[Ing. F. R. <fed...@gm...>]

Dear,
  here's the output for lspci | grep -i usb:



*00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB xHCI Host Controller (rev 04)00:1a.0 USB controller: Intel
Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host
Controller #2 (rev 04)00:1d.0 USB controller: Intel Corporation 7
Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)*


Thanks a lot.


2016-10-08 20:36 GMT+02:00 Ing. Federico Rampin <fed...@gm...>:

> Dear,
>   I'll follow your suggestions Windows side.
>
> No USB hub is involved.
>
> I've been trying in 2 computers, the 1st returns the quoted output, the
> second only a "rkflashtool: fatal: cannot open device".
>
> The strangeness is test al other flashing tools are working, so sounds not
> to be a hardware/drivers issue, correct?
>
> I'll do lspci | grep -i usb under Ubuntu and feedback.
>
> Thanks a lot for support.
>
> Il 08 Ott 2016 8:22 PM, "Ivo van Poorten" <iv...@gm...> ha scritto:
>
>> Hi,
>>
>> On Thu, 6 Oct 2016 17:25:04 +0200 "Ing. Federico Rampin"
>> <fed...@gm...> wrote:
>> > Dears,
>> > I'm trying to do a full NAND backup on Windows with rkflashtool 5.1
>> > (I can succeed on Ubuntu, but on Windows I have several errors).
>> >
>> >[snip...]
>> >
>> > *C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto
>> > ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin rkflashtool:
>> > info: rkflashtool v5.1 libusb: 0.000000 warning [init_device] could
>> > not get node connection information for device
>> > '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
>> > corretto. libusb: 0.000000 error [init_device] device
>> > '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
>> > connected! libusb: 0.015627 error [init_device] device
>> > '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
>> > connected! libusb: 0.062504 warning [init_device] could not get node
>> > connection information for device
>>
>> Looks like your (on board?) USB hub is not supplying the correct node
>> information. Are you connecting the device directly to your motherboard
>> or do you use an external hub in between?
>>
>> You could try updating the drivers for your on board USB and/or
>> external hub to the latest version and see if that works. Or perhaps use
>> an external hub if you are currently not, or the other way around.
>>
>> If none of the above works, could you run:
>>
>> lspci | grep -i usb
>>
>> under Ubuntu?
>>
>> Regards,
>> Ivo
>>
>>

Re: [Rkflashtool-devel] Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows

[Ing. F. R. <fed...@gm...>]

Dear,
  I'll follow your suggestions Windows side.

No USB hub is involved.

I've been trying in 2 computers, the 1st returns the quoted output, the
second only a "rkflashtool: fatal: cannot open device".

The strangeness is test al other flashing tools are working, so sounds not
to be a hardware/drivers issue, correct?

I'll do lspci | grep -i usb under Ubuntu and feedback.

Thanks a lot for support.

Il 08 Ott 2016 8:22 PM, "Ivo van Poorten" <iv...@gm...> ha scritto:

> Hi,
>
> On Thu, 6 Oct 2016 17:25:04 +0200 "Ing. Federico Rampin"
> <fed...@gm...> wrote:
> > Dears,
> > I'm trying to do a full NAND backup on Windows with rkflashtool 5.1
> > (I can succeed on Ubuntu, but on Windows I have several errors).
> >
> >[snip...]
> >
> > *C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto
> > ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin rkflashtool:
> > info: rkflashtool v5.1 libusb: 0.000000 warning [init_device] could
> > not get node connection information for device
> > '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> > corretto. libusb: 0.000000 error [init_device] device
> > '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> > connected! libusb: 0.015627 error [init_device] device
> > '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> > connected! libusb: 0.062504 warning [init_device] could not get node
> > connection information for device
>
> Looks like your (on board?) USB hub is not supplying the correct node
> information. Are you connecting the device directly to your motherboard
> or do you use an external hub in between?
>
> You could try updating the drivers for your on board USB and/or
> external hub to the latest version and see if that works. Or perhaps use
> an external hub if you are currently not, or the other way around.
>
> If none of the above works, could you run:
>
> lspci | grep -i usb
>
> under Ubuntu?
>
> Regards,
> Ivo
>
>

Re: [Rkflashtool-devel] Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows

[Ivo v. P. <iv...@gm...>]

Hi,

On Thu, 6 Oct 2016 17:25:04 +0200 "Ing. Federico Rampin"
<fed...@gm...> wrote:
> Dears,
> I'm trying to do a full NAND backup on Windows with rkflashtool 5.1
> (I can succeed on Ubuntu, but on Windows I have several errors).
>
>[snip...]
> 
> *C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto
> ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin rkflashtool:
> info: rkflashtool v5.1 libusb: 0.000000 warning [init_device] could
> not get node connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.000000 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.015627 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! libusb: 0.062504 warning [init_device] could not get node
> connection information for device

Looks like your (on board?) USB hub is not supplying the correct node
information. Are you connecting the device directly to your motherboard
or do you use an external hub in between?

You could try updating the drivers for your on board USB and/or
external hub to the latest version and see if that works. Or perhaps use
an external hub if you are currently not, or the other way around.

If none of the above works, could you run:

lspci | grep -i usb

under Ubuntu?

Regards,
Ivo

Re: [Rkflashtool-devel] Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows

[Josh S. <jos...@gm...>]

Is this a connection issue?  Does 'rkflashtool p' work?

On Thu, Oct 6, 2016 at 11:25 AM, Ing. Federico Rampin <
fed...@gm...> wrote:

> Dears,
> I'm trying to do a full NAND backup on Windows with rkflashtool 5.1 (I can
> succeed on Ubuntu, but on Windows I have several errors).
>
> Drivers are OK because I can read and write NAND with any other tools, but
> I need rkflashtool because it's the only one I know able to read and write
> the whole NAND to a single file from command line.
>
> I'm on Windows 10 x64 build 1607.
>
> On NU3001-01-H (CPU RK3188) NAND size is 7456MB with 512kB blocks, so
> 7456MB x 1024 = 7634944kB
> 7634944kB / 512kB = 14912 blocks = 0x3A40 blocks
>
> Running as user or admin
>
> *rkflashtool r 0x0 0x3A40 > dump.bin*
>
> or
>
> *rkflashtool r 0 14912 > dump.bin*
>
> I'm returned
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto
> ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin rkflashtool: info:
> rkflashtool v5.1 libusb: 0.000000 warning [init_device] could not get node
> connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.000000 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.015627 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! libusb: 0.062504 warning [init_device] could not get node
> connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.062504 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.062504 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! libusb: 0.078130 warning [init_device] could not get node
> connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.093755 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.093755 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! libusb: 0.109382 warning [init_device] could not get node
> connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.109382 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.125008 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! libusb: 0.140633 warning [init_device] could not get node
> connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.140633 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.140633 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! libusb: 0.156259 warning [init_device] could not get node
> connection information for device
> '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
> corretto. libusb: 0.171886 error [init_device] device
> '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
> connected! libusb: 0.171886 error [init_device] device
> '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
> connected! rkflashtool: fatal: cannot open device *
> I really don't know what to do.
>
> Any suggestions?
>
>
> Thanks and best regards
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Rkflashtool-devel mailing list
> Rkf...@li...
> https://lists.sourceforge.net/lists/listinfo/rkflashtool-devel
>
>

[Rkflashtool-devel] Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows

[Ing. F. R. <fed...@gm...>]

Dears,
I'm trying to do a full NAND backup on Windows with rkflashtool 5.1 (I can
succeed on Ubuntu, but on Windows I have several errors).

Drivers are OK because I can read and write NAND with any other tools, but
I need rkflashtool because it's the only one I know able to read and write
the whole NAND to a single file from command line.

I'm on Windows 10 x64 build 1607.

On NU3001-01-H (CPU RK3188) NAND size is 7456MB with 512kB blocks, so
7456MB x 1024 = 7634944kB
7634944kB / 512kB = 14912 blocks = 0x3A40 blocks

Running as user or admin

*rkflashtool r 0x0 0x3A40 > dump.bin*

or

*rkflashtool r 0 14912 > dump.bin*

I'm returned






















*C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto
ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin rkflashtool: info:
rkflashtool v5.1 libusb: 0.000000 warning [init_device] could not get node
connection information for device
'\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
corretto. libusb: 0.000000 error [init_device] device
'\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
connected! libusb: 0.015627 error [init_device] device
'\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
connected! libusb: 0.062504 warning [init_device] could not get node
connection information for device
'\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
corretto. libusb: 0.062504 error [init_device] device
'\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
connected! libusb: 0.062504 error [init_device] device
'\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
connected! libusb: 0.078130 warning [init_device] could not get node
connection information for device
'\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
corretto. libusb: 0.093755 error [init_device] device
'\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
connected! libusb: 0.093755 error [init_device] device
'\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
connected! libusb: 0.109382 warning [init_device] could not get node
connection information for device
'\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
corretto. libusb: 0.109382 error [init_device] device
'\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
connected! libusb: 0.125008 error [init_device] device
'\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
connected! libusb: 0.140633 warning [init_device] could not get node
connection information for device
'\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
corretto. libusb: 0.140633 error [init_device] device
'\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
connected! libusb: 0.140633 error [init_device] device
'\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
connected! libusb: 0.156259 warning [init_device] could not get node
connection information for device
'\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non
corretto. libusb: 0.171886 error [init_device] device
'\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer
connected! libusb: 0.171886 error [init_device] device
'\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer
connected! rkflashtool: fatal: cannot open device *
I really don't know what to do.

Any suggestions?


Thanks and best regards

[Rkflashtool-devel] (no subject)

[Arne V. <ar...@va...>]

Re: [Rkflashtool-devel] [Rkflashtool-svnlog] SF.net SVN: rkflashtool:[10] trunk/rkflashtool.c

[Ivo v. P. <iv...@eu...>]

Hi,

On Monday 12 March 2012, 12:50:20, Guenter wrote:
> Am 12.03.2012 12:40, schrieb gk...@us...:
> > 2nd trial to kill Ubuntu compile warnings.
> > Seems its now modern to enforce checking of each and every return
> > value; even a cast to void doesnt help for those functions prototyped
> > with the __wur attribute macro. Assigning a var and then not using it
> > will most likely produce the next warning - if not already now then
> > with next gcc ...
> 
> I really hate such crap, but I've no better idea - I think want to
> ignore stdin read() errors since the image can be much smaller than the
> size given and then rkflashtool will pad the rest with 0 - or?

Yes, that was the general idea. You could add -Wno-unused-result to shut gcc 
up if you want. 

> Oh, can you please set the reply-to address of the svnlog list to devel
> since discussion about a commit should be on devel, or do you want it to
> have on svnlog?

I have seen both used by projects, but I guess keeping svnlog clean of 
discussions is better, so I set the reply-to: address. Also changed that of 
-devel to list instead of poster.

Regards,
--Ivo

Re: [Rkflashtool-devel] [Rkflashtool-svnlog] SF.net SVN: rkflashtool:[9] trunk/rkflashtool.c

[Guenter <li...@gk...>]

Hi,
Am 11.03.2012 21:03, schrieb gk...@us...:
> Revision: 9
>            http://rkflashtool.svn.sourceforge.net/rkflashtool/?rev=9&view=rev
> Author:   gknauf
> Date:     2012-03-11 20:03:26 +0000 (Sun, 11 Mar 2012)
> Log Message:
> -----------
> Added hack to set binary mode for stdin / stdout on Windows.
>
> Modified Paths:
> --------------
>      trunk/rkflashtool.c
>
> Modified: trunk/rkflashtool.c
> ===================================================================
> --- trunk/rkflashtool.c	2012-03-11 18:27:28 UTC (rev 8)
> +++ trunk/rkflashtool.c	2012-03-11 20:03:26 UTC (rev 9)
> @@ -37,6 +37,12 @@
>   #include<errno.h>
>   #include<libusb-1.0/libusb.h>
>
> +/* hack to set binary mode for stdin / stdout on Windows */
> +#ifdef _WIN32
> +#include<fcntl.h>
> +int _CRT_fmode = _O_BINARY;
> +#endif
> +
I believe this is a smart hack what I've found; I have tested this hack 
with to565.c (an Android tool for creating *.rle images); with this I 
found 1st that IO redirection on native windows is not binary mode ...
also I've tested a native win32 (MinGW) rkflashtool with writing a 4MB 
image and reading a 160MB image, and that worked fine ...

Gün.

Re: [Rkflashtool-devel] [Rkflashtool-svnlog] SF.net SVN: rkflashtool:[10] trunk/rkflashtool.c

[Guenter <li...@gk...>]

Hi Ivo,
Am 12.03.2012 12:40, schrieb gk...@us...:
> Revision: 10
>            http://rkflashtool.svn.sourceforge.net/rkflashtool/?rev=10&view=rev
> Author:   gknauf
> Date:     2012-03-12 11:40:23 +0000 (Mon, 12 Mar 2012)
> Log Message:
> -----------
> 2nd trial to kill Ubuntu compile warnings.
> Seems its now modern to enforce checking of each and every return value;
> even a cast to void doesnt help for those functions prototyped with the
> __wur attribute macro. Assigning a var and then not using it will most
> likely produce the next warning - if not already now then with next gcc ...
I really hate such crap, but I've no better idea - I think want to 
ignore stdin read() errors since the image can be much smaller than the 
size given and then rkflashtool will pad the rest with 0 - or?

Oh, can you please set the reply-to address of the svnlog list to devel 
since discussion about a commit should be on devel, or do you want it to 
have on svnlog?

Gün.

[Rkflashtool-devel] first changes to rkflashtool

[Guenter <li...@gk...>]

Hi Ivo,
I've meanwhile comitted few changes:
- added an erase option which I find very useful for erasing the idb of 
the device
- changed progress output to stay on one line and output less frequently 
so that it doesnt flicker that much as before

Gün.