Re: sdcc and USB

No hurry...
But thanx.

Ezra.

Am 03.11.2005 um 20:46 schrieb Julian Green:

> ok ill tar it up and send to you then you can host it.   Please  
> allow me
> 24 hours to get home.
>
> Julian
>
> On Thu, 3 Nov 2005, Easy B wrote:
>
>> Cool, I definitely would be interested. I can program 18f2550s, now
>> that I got a working wisp628 setup ;) Haven't you got a website or
>> something? If no, I could host.
>>
>> Cheers,
>> Ezra.
>>
>> Am 03.11.2005 um 19:40 schrieb Julian Green:
>>
>>> I have ported the code to sdcc for the microchip application note
>>> (cant
>>> remember the name) for porting application from rs232 to USB by
>>> implementing a serial port over USB.  No idea if it works, as I cant
>>> program the 2550 chip yet.  Willing to post what I have to the  
>>> list if
>>> people are interested.
>>>
>>> Julian
>>>
>>> On Thu, 3 Nov 2005, Easy B wrote:
>>>
>>>> Hi guys
>>>>
>>>> I'm planning to start programming my new 18F2550 USB PIC with sdcc.
>>>> I'm aware of the examples from microchip and other work based on
>>>> them, but I never found any  code specially for sdcc. Now I'm
>>>> wondering if anybody ported the examples or has some other USB code
>>>> that compiles with sdcc. Or do I have to start from scratch? I know
>>>> that a few guys like Xiao Fan own USB PICs and also use sdcc. I
>>>> really don't want to start programming the 18f parts in assembly,
>>>> everybody is shouting that sdcc works for PICs, especially 18f  
>>>> ones,
>>>> so I want to try that.
>>>> Thanks in advance.
>>>>
>>>> Cheers,
>>>> Ezra.
>>>>
>>>> Am 02.11.2005 um 10:07 schrieb Chen Xiao Fan:
>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: [email protected]
>>>>> [mailto:[email protected]]
>>>>> Sent: Friday, October 28, 2005 3:49 AM
>>>>> To: [email protected]
>>>>> Subject: [Sdcc-user] PIC14 port matures
>>>>>
>>>>>
>>>>> Dear SDCC/PIC14 users,
>>>>>
>>>>> I am really proud to announce that the PIC14 port has seen serious
>>>>> improvement over the past few days:
>>>>>
>>>>> - large quantity of bugs removed
>>>>> - generic pointer support added
>>>>>    Now `unqualified' pointers are three bytes long, use qualifiers
>>>>>    __data or __code to reduce them to two bytes.
>>>>>    Pointers to const "variables" are no longer assumed to point to
>>>>>    __code space; use __code const int *x instead)
>>>>> - better library support has been added
>>>>>    Now the PIC14 port provides better support for multi-source  
>>>>> file
>>>>>    projects (still lacks initialization of variables outside the
>>>>> main
>>>>>    module though, bet works nicely with the library).
>>>>>    All support routines (generic pointer access, multiplication,
>>>>>    division/modulus) should work nicely on a large number of  
>>>>> devices
>>>>>    without recompiling. All projects must link PIC14's
>>>>> libsdcc.lib to
>>>>>    make use of these!
>>>>>    (Volunteers may now start porting a libc...)
>>>>> - a new command-line switch has been added to disable a (slightly)
>>>>>    faulty optimization (--no-pcode-opt).
>>>>>    An improved (and correct ;-D) replacement is under development.
>>>>>
>>>>> Note that .o output from previous SDCC versions will be  
>>>>> incompatible
>>>>> with new ones due to symbol renaming (arguments/return values are
>>>>> now
>>>>> passed on using a location independant `STKn' rather than
>>>>> `s0x<addr>'
>>>>> in order to enable library reuse across multiple devices).
>>>>>
>>>>> I am looking forward to hearing your opinions and bug reports as
>>>>> well as
>>>>> pointers to `most wanted features'.
>>>>>
>>>>> All improvements should be accessible starting with SDCC 2.5.4
>>>>> #1130.
>>>>>
>>>>> Regards,
>>>>>      Raphael Neider
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------ 
>>>>> --
>>>>> -
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>