[En-Nut-Discussion] branches/devnut_m3n: Status of device support
ulrich.prinz at googlemail.com
Wed Oct 19 22:54:27 CEST 2011
What do you guys need all that RAM for?
Think in tables that are declared const and work with pointers, so you
never need so much RAM :)
600 variables of 16 RS485 devices connected to 2 RS485 busses, constants
and variables mapped into CANopen structures. All with a small
STM32F103RBT6 128k FLASH, 20k RAM. Actually testing with 6 connected
devices and still 5k free.
But for the compiler question Henrik asked before:
Use some of the latest gcc version >= 4.5 as there where some issues
with the code generated by the versions between 4.3.x and 4.5.x.
I myself use 4.6.2 with the active devnut_m3n branch.
If you have some issues with that, write mailinglist and copy to my pm,
then I get the trigger.
There is actually to much work and not time left to do the merge into
the trunk. Hope that in exactly 4 weeks everything is calming down an I
get the things back that I forgot the name of...
Ah, yes I googled it: private life... free time... holidays...
On 19.10.2011 10:45, Uwe Bonnes wrote:
>>>>>> "Henrik" == Henrik Maier <hmnews at proconx.com> writes:
> Henrik> On 18/10/2011 9:19 PM, Uwe Bonnes wrote:
> >> Why not go for the F407 and the STM32F4DISCOVERY. You get the stlink
> >> debugging/programming adapter, some devices on-board to test and all
> >> MCU pins brought out to connector pins.
> Henrik> Never considered the F407 before, thanks for the
> Henrik> suggestion. More memory and FPU are nice too have. But at the
> Henrik> end it will come down to part price and availability. The F207
> Henrik> are offered with smaller memory configurations and hence are
> Henrik> considerably cheaper. The beauty of the STM32F line is that
> Henrik> they are all pin-compatible so one up- or downscale depending on
> Henrik> requirements. If we keep the Nut/OS port flexible as well, the
> Henrik> whole range could be supported nicely.
> For development, the F407 might be a good choice. Ample RAM so you can
> upload only to RAM while developping. Debugging/programming on board, so
> somehow self-contained. For the product you can then use a smaller device.
> Did you think about my PCC board proposal?
More information about the En-Nut-Discussion