Search found 237 matches

by faisal
Wed May 01, 2019 3:56 am
Forum: ChibiOS/HAL
Topic: Doubt regarding drivers implementation
Replies: 4
Views: 247

Re: Doubt regarding drivers implementation

If you make it a buffered driver, you can use the hal_serial.h abstraction, as it uses virtual method tables for the implementation. If you need per character interrupts, that would be more like hal_uart - and that is tied to a specific lld file.
by faisal
Thu Apr 11, 2019 4:01 pm
Forum: Development and Feedback
Topic: [NOTE] Things nice to have
Replies: 12
Views: 5227

Re: [NOTE] Things nice to have

Now that the latest kernels and HAL are released, I suggest starting a new thread with ideas for the next significant releases.
by faisal
Wed Apr 10, 2019 7:08 pm
Forum: ChibiOS/RT
Topic: ch.rlist initialization with CH_CFG_NO_IDLE_THREAD
Replies: 3
Views: 705

Re: ch.rlist initialization with CH_CFG_NO_IDLE_THREAD

Hi, When CH_CFG_NO_IDLE_THREAD is enabled then the main() function is the idle thread, you must never try to sleep in there. Doing so causes the problems you are describing. Giovanni Is this still the case? If so, there should be an assert somewhere to catch this. I think chSchGoSleepS is the right...
by faisal
Wed Apr 10, 2019 7:06 pm
Forum: ChibiOS/HAL
Topic: VMT interface between upper and lower level HAL
Replies: 9
Views: 402

Re: VMT interface between upper and lower level HAL

I'm working on a CAN driver for the MCP2515, making it look like a standard hal_can_lld . When I get that working, I'll play with some ideas we're talking about here. Now let's see who gets some code out there first lol :).
by faisal
Tue Apr 09, 2019 6:00 pm
Forum: ChibiOS/HAL
Topic: VMT interface between upper and lower level HAL
Replies: 9
Views: 402

Re: VMT interface between upper and lower level HAL

So, what do you think - should we make something like a BaseCanLLD (following the style of the other single inheritance Base* 'classes') which hal_can would then use?
by faisal
Sun Apr 07, 2019 7:25 pm
Forum: Development and Feedback
Topic: Internal Flash Driver
Replies: 27
Views: 2133

Re: Internal Flash Driver

If you're taking suggestions for the order of including device support, consider the stm32F72x next :)

Thanks for turning your attention to the internal flash driver. We may have some test/example code to contribute for testhal as well. I'll look into it if it would help.
by faisal
Thu Apr 04, 2019 6:23 pm
Forum: ChibiOS/HAL
Topic: VMT interface between upper and lower level HAL
Replies: 9
Views: 402

Re: VMT interface between upper and lower level HAL

Perhaps HAL should go full C++ but I don't know if the world is ready for this :) Giovanni Definitely not ready yet :) ... I'm guessing the VMT should just be part of the driver object. In hal_<device>.c, calls to LLD could be done thru a macro - which either uses the hal_<device>_lld calls directl...
by faisal
Thu Apr 04, 2019 5:52 pm
Forum: ChibiOS/HAL
Topic: VMT interface between upper and lower level HAL
Replies: 9
Views: 402

VMT interface between upper and lower level HAL

I'm currently working on creating a driver for an external SPI to CAN device. I would like to use the hal_can abstraction, but the way HAL is currently designed is that it is directly linked to the hal_<device>_lld functions. I would like to use the HAL to be more than just bound to MCU built-in per...
by faisal
Thu Apr 04, 2019 5:41 pm
Forum: ChibiOS/HAL
Topic: hal_can.h should define CANRxFrame/CANTxFrame
Replies: 1
Views: 67

hal_can.h should define CANRxFrame/CANTxFrame

hal_can.h should define the CANRxFrame/CANTxFrame structures. The structure definitions are currently entirely inside hal_can_lld.h . If there are any platform specific members needed (for example, FMI and TIME in STM32), those should be in macros defined in hal_can_lld.h, and included at the end of...
by faisal
Wed Apr 03, 2019 5:25 pm
Forum: ChibiOS/RT
Topic: Understand difference between stats and time in thread_t
Replies: 9
Views: 222

Re: Understand difference between stats and time in thread_t

Is it true that (assuming no overflow happens), the total time logged by stats for all threads should track the current system time? Also, that the cumulative time for each thread is the actual execution time of the thread + any interrupts that occurred in the thread. The stats timer for the thread ...

Go to advanced search