[En-Nut-Discussion] branches/devnut_m3n: Status of device support

[Henrik Maier]

Hi STM users,

I am looking at using a STM32F207 device in a new project and was 
wondering if below status update us still valid. Has anybody tackled the 
EMAC driver yet?

And which would be the recommended gcc toolchain to use? Yagarto version 
29.04.2011 I suppose?

I am also researching suitable development boards. Looked at ST's and 
the IAR so far. Very limited choice on the market at this stage. And 
what about JTAG adaptors? Could the Turtelizer be used?. Any 
recommendations here would be greatly appreciated.

Cheers

Henrik

On 21/07/2011 8:06 AM, Ulrich Prinz wrote:
>
> On 17.07.2011 16:14, Uwe Bonnes wrote:
>> Hello Ulrich,
>>
>> can you perhaps drop a note on the status of the device support in the devnut_m3n
>> tree? E.g. nut/arch/cm3/dev/stm/stm32_can1.c seems quite usable, but
>> canbus/candemo.c doesn't use it. I will play a little with it and report
>> back...
>
> I try as promised, but here a short overview:
>
> Missing:
> USB(-OTG)
> LCD
> EMAC
> MEM (external memories for STM32F103 devices)
>
> Working:
> USART
> I2C
> GPIO
> ADC (single conversion and DMA conversion)
> PLL (autoconfig at boot, config via nutconf)
> TIM (basic timer functions, some still stmlib state)
> FLASH (self flashing, confnut/confnet in flash)
>
> Partly:
> CAN (only hw-init is working)
> SPI (working but stmlib state)
>
> stmlib state means that it works, but is rather complicated code that is
> optimized for training not for speed or size.
>
> Ulrich
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>