Search found 26 matches
- Thu Apr 04, 2013 10:05 am
- Forum: Development and Feedback
- Topic: chSysInit-Hook and/or chSysInit-Flag
- Replies: 2
- Views: 2778
Re: chSysInit-Hook and/or chSysInit-Flag
Hi Giovanny, thank you for your answer. The system is up after invoking chSysInit() so it is easy enough to set a flag just before calling chSysInit() and check the flag from code called by static initializers. I know this possibility and have implemented it this way already. But there are so many n...
- Wed Apr 03, 2013 8:29 pm
- Forum: Development and Feedback
- Topic: chSysInit-Hook and/or chSysInit-Flag
- Replies: 2
- Views: 2778
chSysInit-Hook and/or chSysInit-Flag
Hi there, i wonder if there is such a thing like a Hook for own code in chSysInit() or a flag which indicates that ChibiOS is up and ready to provide all system-functions. Background of this question is that i'm using ChibiOS in conjunction with C++ and TLSF . Thread-safe allocations are implemented...
- Thu Jan 31, 2013 12:03 pm
- Forum: Development and Feedback
- Topic: [RFC] Ideas for ChibiOS/RT 3.0
- Replies: 63
- Views: 50749
Re: [RFC] Ideas for ChibiOS/RT 3.0
Hi,
I found TLSF a very interesting Project. Perhaps this allocator could be added as a further option besides Memory-pools and heap-allocator.
I found TLSF a very interesting Project. Perhaps this allocator could be added as a further option besides Memory-pools and heap-allocator.
- Sat Sep 22, 2012 9:40 am
- Forum: General Support
- Topic: Linking problems with Chibi-Studio
- Replies: 5
- Views: 5815
Re: Linking problems with Chibi-Studio
Thanks for the quick answer. I'll implement these stubs then.
- Sat Sep 22, 2012 9:12 am
- Forum: General Support
- Topic: Linking problems with Chibi-Studio
- Replies: 5
- Views: 5815
Re: Linking problems with Chibi-Studio
Unfortunately did this not solve the problem. Still linking errors: c:/chibistudio/tools/gnu tools arm embedded/4.6 2012q2/bin/../lib/gcc/arm-none-eabi/4.6.2/../../../../arm-none-eabi/lib/armv7e-m\libc.a(lib_a-abort.o): In function `abort': abort.c:(.text.abort+0xa): undefined reference to `_exit' c...
- Sat Sep 22, 2012 8:34 am
- Forum: General Support
- Topic: Linking problems with Chibi-Studio
- Replies: 5
- Views: 5815
Linking problems with Chibi-Studio
Hi there, I'm having problems linking projects with vanilla Chibi-Studio: c:/chibistudio/tools/gnu tools arm embedded/4.6 2012q2/bin/../lib/gcc/arm-none-eabi/4.6.2/../../../../arm-none-eabi/lib/armv7e-m\libc.a(lib_a-sbrkr.o): In function `_sbrk_r': sbrkr.c:(.text._sbrk_r+0xc): undefined reference to...
- Mon Sep 10, 2012 1:00 pm
- Forum: Development and Feedback
- Topic: Deletion of mail.c
- Replies: 2
- Views: 2884
Deletion of mail.c
Hi,
will os/varios/mail.[ch] be put back to trunk again, or will it stay deleted? For what reason it got deleted?
Thanks in advance.
will os/varios/mail.[ch] be put back to trunk again, or will it stay deleted? For what reason it got deleted?
Thanks in advance.
- Tue Jun 26, 2012 10:53 am
- Forum: Development and Feedback
- Topic: Next generation RTOS
- Replies: 28
- Views: 19941
Re: Next generation RTOS
[...] my problem is mainly with portability of such an approach, currently ChibiOS is portable even to the most #$%##$ proprietary compilers. If written in C++ it would be limited to G++ and very few decent and expensive commercial compilers. [...] I'd suspect that gcc/g++ is the compiler of choice...
- Tue Jun 26, 2012 8:51 am
- Forum: Development and Feedback
- Topic: Next generation RTOS
- Replies: 28
- Views: 19941
Re: Next generation RTOS
My suggestion for the next generation of ChibiOS would be ChibiOS++, a C++ implementation of ChibiOS, and not just a wrapper. Especially, I feel that the HAL and device driver implementation should be moved. Being an OOP, it'd probably simplify portability problems across hardware a lot. Totally ag...
- Mon May 14, 2012 6:59 am
- Forum: General Support
- Topic: problem with frequent call of chIOGetTimeout( )
- Replies: 9
- Views: 5731
Re: problem with frequent call of chIOGetTimeout( )
Hi, i've managed to solve the issue: The reason for this phenomenon was defective hardware. The RF-Module was continously throwing rx-interrupts even if no data was incomming via RF and the MCU put the delivered garbage into the queue. Due lack of Oscilloscope it took some time to debug this by LED-...