Re: Specific needs on stm32

Valentin

What eCos version are you using? 3.0 doesn't have STMF4 BSP and STMF1
won't work on STMF4.
You need eCos from CVS - look for the link in my previous mail.

After you get eCos from CVS you need to set configtool to use it
(Build->Repository then navigate to CVS repository).
Now you should be able to see STMF4 target(s) in configtool templates.

Ilija


On 24.01.2014 11:32, Valentin BOUSSON wrote:
> Hi !
>
> Thank you for your enducement.
> I read a lot more about the user guide, and it seems really adapted.
>
> As a first step, I am trying to make a simple hello world functionning
> on my stm32f4 discovery , and that's not so easy.
>
> I downloaded the ecos-3.0 via the  "ecos-install.tcl" script, and it
> did well. I add into my PATH the gnu-tools binaries, to use all the
> arm-eabi prefixed tools.
> Then I ran the ecosconfig from a separate folder "work", in which I
> put hello.c and a Makefile created with build_Makefile (and modifying
> the SRCS, OBJS, etc..)
>
> My folder structure is :
> ecos
> ├── ecos-3.0
> │   └── ...
> ├── ecosenv.csh
> ├── ecosenv.sh
> ├── gnutools
> │   └── arm-eabi
> │        └── ...
> └── work
>      ├── app
>      │   ├── hello.c
>      │   ├── Makefile
>      │   └── Make.params
>      ├── my_stm32f4_build
>      │   └── ...
>      ├── my_stm32f4.ecc
>      └── my_stm32f4_install
>           └── ...
>    
> The compilation process is going well, and I have now a hello.o, which
> I can compile into an executable with the following command I have
> adapted.
> /TARGET-/gcc -g -I/BASE_DIR//ecos-work/install/include hello.c -L/BASE_DIR//ecos-work/install/lib -Ttarget.ld -nostdlib
>
>
>
> I think my problem now is very platform-specific because I'm unable to
> make this executable to work neither onto the stm32, neither on a
> simulator (arm-eabi-run ??).
> I used to write my tests with the qstlink2 utility to flash my memory
> in SWD, but the stm23f4 don't react at all, nor reboot. Some leds are
> on but, no idea.
>
> I try to use the official st-util, in order to use a remote gdb, but I
> don't know how to do.
>
>
> In your opinion, I am on the good way with my experiments ?
>
>
> And then, I saw nowhere in the eCos hal/stm32 folders the officials
> BSP, as the management of GPIO, or SDIO, etc...
>
>
> Thanks a lot.
>
> Valentin BOUSSON
>
>
> On 20/01/2014 21:04, "Ilija Kocho [Илија Кочо]" wrote:
>> Hi Valentin
>>
>>
>>
>> On 20.01.2014 17:12, Valentin BOUSSON wrote:
>>> Hi all, I'm fresh and new on this mailing list,
>>> and in the world of real embedded systems, actually.
>>>
>>> I bought a STM32F4 - DISCOVERY board to play with, and I succeeded to
>>> compile and run a lot of simple, led / LCD / audio project I found
>>> online. I was using the Sourcery arm compile chain for that.
>>>
>>> But my next ambition is little harder, I would like to adapt one of my
>>> existing program, based on a plugin-mechanism, on my stm32. So, I was
>>> looking for an RTOS being able to manage a simple system, in the Flash
>>> memory, or in an external SD card.
>>>
>>>
>>>
>>>
>>> I tried to set up the compilation environnement described in the big
>>> pdf describing eCos, and on the Download & Installation section on the
>>> website, I tried all the day, without any result.
>>> Do you have some good links / tuto / advices to share ?
>>>
>> You need to get eCos from CVS (that I prefer to call "the rolling release").
>> Here you'll find info how to access CVS
>> http://ecos.sourceware.org/anoncvs.html
>>
>> Also you can try eCos arm-eabi GNU tools - test release 4.6.3
>> http://ecos.sourceware.org/ml/ecos-discuss/2012-06/msg00047.html
>> that comes with support for hardware floating point.
>>
>>> My questions are :
>>> Is it possible to use the compilation chain generated by
>>> summon-arm-toolchain, to compile eCos itself ?
>> I haven't tried it.
>>
>>> What about the programs I would like to run on top of eCos ?
>>>
>> What would you like to run?
>> With this little information, I can just say that porting POSIX
>> applications is relatively straight forward.
>>
>>> If I store my programs in the Flash, how can I reprogram the flash to
>>> change only the program, and not the kernel ?
>>>
>> Kernel is in general being linked with application. However it is
>> possible to create dynamically loadable libraries.
>> Also, you can install RedBoot and then use it for loading applications.
>>
>>> IYO, is eCOS the best OS to choose for my project ? // Are its dynamic
>>> loading mechanism easy to use ?
>>>
>> No one can tell you what's best for your project. But IMHO, eCos is
>> worth for consideration.
>> I encourage you to try it.
>>
>> Have fun
>>
>> Ilija
>>
>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss