Search found 11 matches
- Sun Feb 21, 2016 11:56 pm
- Forum: STM32 Support
- Topic: ChibiOS/RT 2.6.7 STM32F407 CCM linker error
- Replies: 2
- Views: 1715
Re: ChibiOS/RT 2.6.7 STM32F407 CCM linker error
Switching to 3.1 made it the CCM work. Thank you very much.
- Sun Feb 21, 2016 11:55 pm
- Forum: ChibiOS/RT
- Topic: [FEATURE REQUEST] More hooks
- Replies: 13
- Views: 5652
Re: [FEATURE REQUEST] More hooks
Thank you. That works. I have to do the locking outside the kernel on my own with this solution, but that should be no problem.
Now I ran in a stack overflow issue. I have the feeling that I have to make all stacks bigger or I didn't find the offending stack yet.
Now I ran in a stack overflow issue. I have the feeling that I have to make all stacks bigger or I didn't find the offending stack yet.
- Sun Feb 21, 2016 9:10 pm
- Forum: ChibiOS/RT
- Topic: [FEATURE REQUEST] More hooks
- Replies: 13
- Views: 5652
Re: [FEATURE REQUEST] More hooks
I just found this thread because I try to add Segger SystemView support to my project which is based on ChibiOS 3.1 at the moment. I tried to use the context switch hook but I ran into locking errors. The SystemView integration sources don't have anything like the I-class API. #define CH_CFG_CONTEXT...
- Tue Aug 18, 2015 8:44 pm
- Forum: STM32 Support
- Topic: ChibiOS/RT 2.6.7 STM32F407 CCM linker error
- Replies: 2
- Views: 1715
ChibiOS/RT 2.6.7 STM32F407 CCM linker error
Hello, when my project was small I used used the $(PORTLD)/STM32F407xG_CCM.ld linker script. Everything worked nicely. But when my project grew linking with that script started to fail. Disabling the debug features of ChibiOS/RT helped at first, but now even that doesn't help. And the debug features...
- Tue Jun 30, 2015 9:10 pm
- Forum: General Support
- Topic: lwIP start race condition (patch)
- Replies: 9
- Views: 3633
Re: lwIP start race condition (new patch)
Hello, I have expanded the optional parameter of the lwip_thread() function. It now carries a function pointer and a parameter pointer which are passed to tcpip_init(). This should be compatible with all existing code. Just starting lwip_thread with a high priority did not work when I used a hardwar...
- Sun Jun 28, 2015 10:30 pm
- Forum: General Support
- Topic: lwIP start race condition (patch)
- Replies: 9
- Views: 3633
Re: lwIP start race condition (patch)
Hello, the lwIP thread should have the highest possible priority then but you still have to be careful that nothing you include starts at an equally high priority. I didn't see that a thread function can only have one argument because I used the C++ API to create the thread. A proper way to use that...
- Sun Jun 28, 2015 7:50 pm
- Forum: General Support
- Topic: lwIP start race condition (patch)
- Replies: 9
- Views: 3633
lwIP start race condition (patch)
Hello, using any function of lwIP before it completed its initialization usually ends in a crash. lwIP is initialized when its thread starts. So you have a race condition if you are using lwIP just after starting its thread. To prevent that you can pass a callback function to tcpip_init() which is c...
- Mon Mar 21, 2011 10:07 pm
- Forum: Open Discussion about the Commercial Options
- Topic: License when it is impossible to reflash the microcontroller
- Replies: 3
- Views: 6362
Re: License when it is impossible to reflash the microcontro
Hello Giovanni, thank you for the clarification. what troubles me is this clause: "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product f...
- Mon Mar 21, 2011 8:32 pm
- Forum: Open Discussion about the Commercial Options
- Topic: License when it is impossible to reflash the microcontroller
- Replies: 3
- Views: 6362
License when it is impossible to reflash the microcontroller
Hello,
is the commercial license the only way to use ChibiOS/RT when it is impossible to reflash the microcontroller?
Frank
is the commercial license the only way to use ChibiOS/RT when it is impossible to reflash the microcontroller?
Frank
- Wed Dec 15, 2010 3:24 am
- Forum: General Support
- Topic: Problems debugging with Eclipse
- Replies: 2
- Views: 2902
Re: Problems debugging with Eclipse
Hi,
problem one got solved by an CDT update.
You OpenOCD configuration is almost working with version 0.4.0.
gdb_memory_map enable
gdb_flash_program enable
Give an error message, but both are default any way.
Thank you very much.
Frank
problem one got solved by an CDT update.
You OpenOCD configuration is almost working with version 0.4.0.
gdb_memory_map enable
gdb_flash_program enable
Give an error message, but both are default any way.
Thank you very much.
Frank