gnupic: Re: [gnupic] RE: fsusb-0.1.11 problem


Previous by date: 11 Aug 2005 02:03:01 +0100 byte data in code space on 16 bit devices, Peter Onion
Next by date: 11 Aug 2005 02:03:01 +0100 Re: [gnupic] RE: fsusb-0.1.11 problem, Manwlis Giannos
Previous in thread: 11 Aug 2005 02:03:01 +0100 Re: [gnupic] RE: fsusb-0.1.11 problem, Manwlis Giannos
Next in thread: 11 Aug 2005 02:03:01 +0100 Re: [gnupic] RE: fsusb-0.1.11 problem, Manwlis Giannos

Subject: RE: T?µa: [gnupic] RE: fsusb-0.1.11 problem
From: Chen Xiao Fan ####@####.####
Date: 11 Aug 2005 02:03:01 +0100
Message-Id: <3B8AEFFADD3DD4118F8100508BACEC2C07F77436@spex>

I do not quite understand you. So you reverse engineered
the hex file and produce the assembly version of the USB
firmware. That is of course interesting. But I doubt if it
is legal to stick a GPL on reverse engineered code
but I am not a legal expert. Anyway what you do is 
interesting work. It is quite difficult to assemble
a really decent version from reverse engineering as
well.

Another thing is that the firmware source code is there for
the MPLAB C18. MPLAB C18 student version is free and is
working under Linux with Wine as well. There is also a 
version for Hitech PICC on the PICC forum. It would be great 
to port it to SDCC if possible.

Still have you checked the USB section of Microchip Forum? 
There is an assembly based implementation from Olin college.
http://pe.ece.olin.edu/ece/


Regards,
Xiaofan

-----Original Message-----
From: Manwlis Giannos ####@####.####
Sent: Wednesday, August 10, 2005 8:58 PM
To: ####@####.####
Subject: T?µa: [gnupic] RE: fsusb-0.1.11 problem
Apart from what you are doing concerning "PIC FS USB
demo board" i have succeeded, I HOPE, something
interesting... I explain:
I have downloaded the file "MCHPFSUSB.ZIP" from
Microchip's site. This file contains a lot of "C" code
 examples and interesting matching "hex" files. If you
have a good programmer and a good programmer IDE
environment (My name is "Pikdev") you can download
whatever "hex" into a PIC18F4550. You will notice that
"usbview" sees it. Further more, you can reverse
engineer the hex files and finally construct a decent
"asm" code. If you want to modify it and make it suit
your needs you are another step forward (and you will
never need a "PIC-dedicated" C compiler). Moreover you
need a USB dev. driver. What about to stick a "GPL"
licence to them? What do you think? Do you want to
take a look? In case you want i'll send a "gz"
tarball. 

"Manos"



Previous by date: 11 Aug 2005 02:03:01 +0100 byte data in code space on 16 bit devices, Peter Onion
Next by date: 11 Aug 2005 02:03:01 +0100 Re: [gnupic] RE: fsusb-0.1.11 problem, Manwlis Giannos
Previous in thread: 11 Aug 2005 02:03:01 +0100 Re: [gnupic] RE: fsusb-0.1.11 problem, Manwlis Giannos
Next in thread: 11 Aug 2005 02:03:01 +0100 Re: [gnupic] RE: fsusb-0.1.11 problem, Manwlis Giannos


Powered by ezmlm-browse 0.20.