Hi, I have a project in arm-elf-gcc (ported from avr-gcc), works well. I have an usb mass storage source in IAR, i want use this in my project with an SD card. How can I use this from arm-gcc, which is the simplest way? ( I have never used IAR EWBARM (only in z80 :), and all my projects are in gcc from embedded linux to the OS-less microcontroller systems ) Thanks Andras
How to use IAR source in a arm-elf-gcc project
Started by ●March 19, 2006
Reply by ●March 19, 20062006-03-19
> I have a project in arm-elf-gcc (ported from avr-gcc), works well.
> I have an usb mass storage source in IAR, i want
use this in my project
> with an SD card.
>
> How can I use this from arm-gcc, which is the simplest way?
> ( I have never used IAR EWBARM (only in z80 :), and all my projects are
> in gcc
> from embedded linux to the OS-less microcontroller systems )
Compile IAR code as library and set linker to generate Elf/Dwarf output.
See end of your .xcl file:
//*************************************************************************
// ELF/DWARF support.
//
// Uncomment the line "-Felf" below to generate ELF/DWARF output.
// Available format specifiers are:
//
// "-yn": Suppress DWARF debug output
// "-yp": Multiple ELF program sections
// "-yas": Format suitable for debuggers from ARM Ltd (also sets -p
flag)
//
// "-Felf" and the format specifiers can also be supplied directly as
// command line options, or selected from the Xlink Output tab in the
// IAR Embedded Workbench.
//*************************************************************************
// -Felf
Joel
Reply by ●March 19, 20062006-03-19
Last year I ported the USB mass storage to Crossworks for ARM. (which is GCC). There's a few things to change, mainly the packing of the CSW and CBW wrapper structs, and __ramfunc must become 'fast' section. There's actually 2 bugs in that code. I can't disclose it under the license of Atmel, but perhaps I can ask Atmel to see if they'll allow release under Crossworks ? B rgds Kris -----Original Message----- From: AT91SAM@AT91... [mailto:AT91SAM@AT91...] On Behalf Of Kalyos Vendel Sent: Sunday, 19 March 2006 10:59 PM To: AT91SAM@AT91... Subject: [AT91SAM] How to use IAR source in a arm-elf-gcc project Hi, I have a project in arm-elf-gcc (ported from avr-gcc), works well. I have an usb mass storage source in IAR, i want use this in my project with an SD card. How can I use this from arm-gcc, which is the simplest way? ( I have never used IAR EWBARM (only in z80 :), and all my projects are in gcc from embedded linux to the OS-less microcontroller systems ) Thanks Andras Yahoo! Groups Links
Reply by ●March 20, 20062006-03-20
--- In AT91SAM@AT91..., "Microbit" <microbit@...> wrote:
>
> Last year I ported the USB mass storage to Crossworks for ARM.
> (which is GCC).
> There's a few things to change, mainly the packing of the CSW and CBW
> wrapper structs, and __ramfunc must become 'fast' section.
> There's actually 2 bugs in that code.
> I can't disclose it under the license of Atmel, but perhaps I can ask
> Atmel to see if they'll allow release under Crossworks ?
Please do ask them! This would be a great example.
They should at least agree to let you disclose the bugs and the fixes.
I don't think they'd want to hide that. But I think they'll agree
to
release the whole thing.
Try emailing arm91support at atmel.com if you don't already have an
Atmel contact.
Eric
Reply by ●March 20, 20062006-03-20
Hi Eric,
I'll try that.
The main bug is the initialisation of the FIFO pointers on cold start.
You might have noticed that running cold start on the EK by only plugging in
USB as power doesn't work....
The other bug has to do with reading files under the FAT12/16.
-- Kris
-----Original Message-----
From: AT91SAM@AT91... [mailto:AT91SAM@AT91...] On Behalf Of Eric Engler
Sent: Monday, 20 March 2006 3:34 PM
To: AT91SAM@AT91...
Subject: [AT91SAM] Re: How to use IAR source in a arm-elf-gcc project
--- In AT91SAM@AT91..., "Microbit" <microbit@...> wrote:
>
> Last year I ported the USB mass storage to Crossworks for ARM.
> (which is GCC).
> There's a few things to change, mainly the packing of the CSW and CBW
> wrapper structs, and __ramfunc must become 'fast' section.
> There's actually 2 bugs in that code.
> I can't disclose it under the license of Atmel, but perhaps I can ask
> Atmel to see if they'll allow release under Crossworks ?
Please do ask them! This would be a great example.
They should at least agree to let you disclose the bugs and the fixes.
I don't think they'd want to hide that. But I think they'll agree
to
release the whole thing.
Try emailing arm91support at atmel.com if you don't already have an
Atmel contact.
Eric
Yahoo! Groups Links