Giovanni,
Is there some documentation that you can point us to on the best way to do
pin configuration management. I am hand editing the board.h file to enable
/ disable pins for my code but not all the pins are defined in board.h. i.e.
For my STM32F4 discovery board, there was a board.h but the ...
Search found 11 matches
- Fri Feb 15, 2013 12:26 am
- Forum: Development and Feedback
- Topic: board config
- Replies: 28
- Views: 29076
- Sun Nov 25, 2012 2:36 pm
- Forum: General Support
- Topic: Help with SDIO/FATFS on STM32F4 Discovery
- Replies: 2
- Views: 3651
Re: Help with SDIO/FATFS on STM32F4 Discovery
Grazie Giovanni, that was the issue..
- Sun Nov 25, 2012 11:04 am
- Forum: General Support
- Topic: Help with SDIO/FATFS on STM32F4 Discovery
- Replies: 2
- Views: 3651
Help with SDIO/FATFS on STM32F4 Discovery
I have a STM32F4 Discovery board that is attached to one of these expansion boards you can get on EBay, the Open407V-D, and my code is based off of the ARMCM4-STM32F407-LWIP-FATFS-USB demo project.
On startup I init the SDC stack and register my events with
sdcStart(&SDCD1, &sdccfg);
tmr_init ...
On startup I init the SDC stack and register my events with
sdcStart(&SDCD1, &sdccfg);
tmr_init ...
- Fri Sep 28, 2012 9:27 pm
- Forum: General Support
- Topic: STM32F4, C++ Exception handling support ?
- Replies: 2
- Views: 2912
STM32F4, C++ Exception handling support ?
Is it possible/practical to enable C++ Exception handling support using the
Yagarto toolchain or does it just add too much overhead ?
I have a C++ library that I want to incorporate into my project but any throw()
call winds up in the unhandled exception function and not in the catch block.
I ...
Yagarto toolchain or does it just add too much overhead ?
I have a C++ library that I want to incorporate into my project but any throw()
call winds up in the unhandled exception function and not in the catch block.
I ...
- Thu Jul 26, 2012 11:57 am
- Forum: User Projects
- Topic: Example code for STM32F4 Discovery
- Replies: 19
- Views: 29918
Re: Example code for STM32F4 Discovery
I totally missed the USB-CDC in testhal.. To answer your question, yes I can compile and run that code just fine which is what I was looking for..
I still get the linker with your Github project, the only differences I found in the Makefile's were
USE_FPU = no
the include $(CHIBIOS)/test/test.mk is ...
I still get the linker with your Github project, the only differences I found in the Makefile's were
USE_FPU = no
the include $(CHIBIOS)/test/test.mk is ...
- Thu Jul 26, 2012 11:15 am
- Forum: User Projects
- Topic: Example code for STM32F4 Discovery
- Replies: 19
- Views: 29918
Re: Example code for STM32F4 Discovery
Hi,
I am trying to compile this project but I am getting a link error missing the syscalls stubs..
I found another article pointing to a stubs project on github but it appears to be a dead project.
Are there any other pointers out there to code / settings that will satisfy the linker error ?
Thank ...
I am trying to compile this project but I am getting a link error missing the syscalls stubs..
I found another article pointing to a stubs project on github but it appears to be a dead project.
Are there any other pointers out there to code / settings that will satisfy the linker error ?
Thank ...
- Tue Jul 24, 2012 12:05 am
- Forum: General Support
- Topic: Problem compiling ChibiOS with -O0 (no opt)
- Replies: 6
- Views: 4721
Re: Problem compiling ChibiOS with -O0 (no opt)
I now notice that the standard C/C++ run configuration hangs because st-util terminates
after the load command so it's waiting for a response from st-link from the run command.
My gdbinit is as follows.
file build/ch.elf
br main
target extended-remote 127.0.0.1:4242
load
load works, then st-util ...
after the load command so it's waiting for a response from st-link from the run command.
My gdbinit is as follows.
file build/ch.elf
br main
target extended-remote 127.0.0.1:4242
load
load works, then st-util ...
- Mon Jul 23, 2012 10:14 pm
- Forum: General Support
- Topic: Problem compiling ChibiOS with -O0 (no opt)
- Replies: 6
- Views: 4721
Re: Problem compiling ChibiOS with -O0 (no opt)
Wow I did not expect that to work.. SF only has 4.6.2 for the Mac as a download so I gave it a try
and it worked under Eclipse using the Zylin native CDT GDB connector.. The standard default C/C++
application run configuration sill fails..
4.7.1 works, it just doesn't work using the Zylin Native ...
and it worked under Eclipse using the Zylin native CDT GDB connector.. The standard default C/C++
application run configuration sill fails..
4.7.1 works, it just doesn't work using the Zylin Native ...
- Sat Jul 21, 2012 9:25 pm
- Forum: General Support
- Topic: Problem compiling ChibiOS with -O0 (no opt)
- Replies: 6
- Views: 4721
Re: Problem compiling ChibiOS with -O0 (no opt)
Interestingly I would of sworn this problem was the same with the command line version of GBD but after
re-reading the texane page, I saw that I needed to specify the target with extended-remote and not just
remote. This gave me the kill and run commands, now the command line works just fine and it ...
re-reading the texane page, I saw that I needed to specify the target with extended-remote and not just
remote. This gave me the kill and run commands, now the command line works just fine and it ...
- Sat Jul 21, 2012 6:13 am
- Forum: General Support
- Topic: Problem compiling ChibiOS with -O0 (no opt)
- Replies: 6
- Views: 4721
Re: Problem compiling ChibiOS with -O0 (no opt)
Forgot to mention this is on a STM32 F4 Discovery board, running the vanilla board demo code