New STM32F0 devices (Cortex-M0)

[Giovanni]

Thanks, I will update the file with the one from the library ASAP.

About the GDB server, once OpenOCD 0.6.0 will be released the Atollic server will no more be required (it is not a bad server anyway, it just works), my problem is more with the fact to have to rely on something is not really open and accessible. Setting up an entirely open environment may take some time and effort but after that you are really free.

Giovanni

[Jacon]

(it is not a bad server anyway, it just works)

Exactly - and I would add "today" to the end of above quote, cause we don't have any clue
about their plans.
They may "just" close GDB in next Lite release, as IDE is closed now...

[8bitgeek]

Thanks, I will update the file with the one from the library ASAP.

About the GDB server, once OpenOCD 0.6.0 will be released the Atollic server will no more be required (it is not a bad server anyway, it just works), my problem is more with the fact to have to rely on something is not really open and accessible. Setting up an entirely open environment may take some time and effort but after that you are really free.

Giovanni

I'm using STM3250DISCOVERY PCB with ST-LINK/2 and OpenOCD:

Code: Select all

Open On-Chip Debugger 0.6.0-dev-00599-ga21affa (2012-06-12-00:24)

Here's my scripts:

init.gdb

Code: Select all

#Initialize ARM GDB for OpenOCD debugging
#######################################
#setup search directories
directory ./
directory codeblocks/bin/Debug
directory libpa
directory libpa110
directory ../../chibios/os/kernel/include
directory ../../chibios/os/ports/GCC/ARMCMx
directory ../../chibios/os/ports/GCC/ARMCMx/STM32
directory ../../chibios/os/hal/include
directory ../../chibios/os/hal/platforms/STM32
directory ../../chibios/boards/ST_STM32F0_DISCOVERY
directory ../../chibios/test

file pa1100.elf

set architecture auto
target remote localhost:3333
mon reset halt
mon wait_halt 500
mon poll on

#set some debugging parameters
set print demangle on
set print pretty on

break ResetHandler
break main
cont

pa10-stlink-stm32-debug.cfg

Code: Select all

#
# Stm32 DIscovery Dev Board

source [find board/stm32f0discovery.cfg]

#gdb_breakpoint_override  hard
gdb_memory_map disable
gdb_flash_program enable
init 
#reset halt

start_openocd-stlink.sh

Code: Select all

#!/bin/bash
openocd --search /usr/local/share/openocd/scripts -f pa10-stlink-stm32-debug.cfg &

--8bitgeek

[Tectu]

complelty offtopic:

8bitgeek using 32-bit MCUs - awesome


~ Tectu

[Giovanni]

Update, all the applicable device drivers except UART and RTC tested on the F0. I2C is missing and will require a different implementation because the peripheral is very different.

Edit: UART is working too now.

Giovanni

[mobyfab]

Awesome, good job

I guess you can add it to the wiki, as it is not listed right now.(In the HAL support)

I need to grab one as I have a project using one of these.

[alexblack]

Hi,
How about to add support of STM32F0xx devices in IAR?

[Giovanni]

Those are already supported under IAR, reports are not available because the free IAR is limited to 8K and the test suite is larger than that.

Giovanni

[alexblack]

Hmm. I don't anderstand.
I was confused that the folder ..\os\ports\IAR\ARMCMx\ does not contain specific files for M0 port like GCC port such as crt0.c and subfolder STM32F0xx and so..
Is it right? Which files I must include in project for vectors for example?

p.s. I am trying 2.7.x OS version from trunk.

[Giovanni]

Ah understood, you just need to create the folder and those files taking them from another M0 device. I will add them if you are not in a hurry.

Giovanni