ecos-3.0 current stm32 bug?

["Philipp Meier" <pme.neratec@xxxxxx>]

Hi all

I have a firmware split into two parts:
 1. a "bootloader"
 2. a "application"

I now need to move from Windows (cygwin) development environment to Linux development environment and at the same time use the current ecos version (i.e. what I get when I clone the ecos mercurial repository) instead of the "original" (back in 2009) ecos-3.0 version.

The situation is now as follows:
 1. I download (to my stm32 device) the Linux/ecos-current built "bootloader"
 2. I download (to my stm32 device) the Linux/ecos-current built "application"
 3. I start the application and in line 187 of file 'hal/cortexm/arch/current/src/hal_msic.c' instead of branching to 'hal_switch_state_vsr' it branches to 'hal_default_exception_vsr' function!

To analyze the problem I then:
 4. Downloaded (to my stm32 device) the cyginw/ecos-3.0 built "bootloader"
 5. Still having the Linux/ecos-current built "application"
 6. And in line 187 (of the above mentioned file) it branches (as it should) to 'hal_switch_state_vsr' and the application is starting up and running fine!

Who can give me a hint about
 * what has been changed in ecos-current cortexm stm32 that could cause this problem
 * or what else I could analyze to find out why ecos-current (built on Linux, arm-eabi-gcc (eCosCentric GNU tools 4.3.2-sw); under cygwin I also used the arm-eabi-gcc version 4.3.2 pre-built by eCosCentric)

Regards
Philipp

-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!		
Jetzt informieren: http://www.gmx.net/de/go/freephone

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