[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] using the 43USB355 (was - Using IAR compiled lib w

From: Jason Kyle
Subject: Re: [avr-gcc-list] using the 43USB355 (was - Using IAR compiled lib with GCC?)
Date: Mon, 01 Sep 2003 22:09:17 +1200

At 09:24 01/09/2003 +0200, Bryan Jarmain wrote:
I recently tried to use the AT43USB355, but could not get the USB side to
work, even after quite considerable effort. I found the root cause to be
inadequately and inaccurately documented hardware (USB) functionality. The
rest of the device seemed easy enough to use (although considering there is
no emulator support - I implemented a 115kbaud bit-bang serial port in
software for this purpose).

Atmel sent me some beta 43USB355 USB libraries with a wizard (I believe they
may be properly released now), but I was reluctant to use them because their
source code was not open (proprietary) - I don't believe using closed
libraries is an industrial standard way of writing firmware. Especially with
the library having such a fundamental influence on the firmware structure
(e.g. no main function in your C code). They also didn't provide other
source-code examples on how to use their USB hardware features - I couldn't
even initialize the USB functionality.

Anyway, to cut a long story short I decided it would be prudent to find a
better documented USB device (where I had better knowledge and understanding
of what was happening behind the scenes), until Atmel decides to better
document the 43USB355 (and hopefully expose their library source code )...

All this was a pity because the 43USB355 seems to be a very nice
microprocessor with lots of promise. Currently it is probably very usable
for anyone who is prepared to use Wizards and Proprietary Libraries (they
claim their libraries are quite stable - I have no reason to doubt this). I
just believe it still needs a bit of work from their side before it becomes
a widely acceptable micro.

Next year we should see some decent USB micros from Atmel, the current crop is based around the original AVR core. Hopefully Atmel (hint hint) will prepare both open (for gcc) and proprietary (for IAR C & others) libraries for the new batch of USB AVR's. All this proprietary talk reminds me of the FPSLIC devices, is anybody still using them?

Jason Kyle

Has anyone been successful with this device (without using their libraries).
If anyone has had success and has source-code to share, I would be very
interested to see some example code on the hardware interface.


-----Original Message-----
From: Keith Gudger [mailto:address@hidden
Sent: Friday, August 29, 2003 6:14 PM
To: Tim Lapawa
Cc: address@hidden
Subject: Re: [avr-gcc-list] Using IAR compiled lib with GCC?

I have USB libraries for the AT43USB35x USB AVRs, compiled for GCC.  I
haven't gotten the 320 libraries compiled for GCC yet, but there is a
io43u32x.h file, and one can set -mmcu=at43usb320. (WinAVR release, at

I can send you the 35x files anytime, but I will have to compile the 32x
libraries next week (when I'm back from vacation ;) ).


On Fri, 29 Aug 2003, Tim Lapawa wrote:

> Hello list,
> atmel send me a proprietary library for the AT43USB320 SDK kit.
> It's an 4port USB Hub with integrated 8515 integrated.
> But they do not want to send me the firmwares source code.
> They send me libraries compiled with the IAR and the Imagecraft compiler.
> Can I use these libs with the GNU toolchain?
> I've read in this list, that the IAR and the GNU compiler use
> different registers for Stack- and Framepointer.
> And what is about parameter passing in function calls?
> Greetings Tim Lapawa
> --

reply via email to

[Prev in Thread] Current Thread [Next in Thread]