Search found 264 matches

by faisal
Fri Feb 22, 2019 2:41 am
Forum: Small Change Requests
Topic: testhal: Separate portable parts of HAL structs from non-portable
Replies: 1
Views: 554

testhal: Separate portable parts of HAL structs from non-portable

In testhal, the various HAL peripheral configuration structures are continuously redefined in the portab.c/h files. The configuration structures should be defined in the actual application code (main.c in all the testhal applications I've seen ...), and the non-portable board specific parts of the s...
by faisal
Fri Feb 22, 2019 2:25 am
Forum: ChibiOS/RT
Topic: undefined reference to ST2MS and MS2ST
Replies: 21
Views: 3880

Re: undefined reference to ST2MS and MS2ST

Your QMKUSBDriverVMT struct inherits from BaseSequentialStream in hal_stream.h. That has been updated to add _base_object_methods (hal_objects.h) used for multiple inheritance. _base_object_methods just contains a size_t instance_offset; . So add a "(size_t)0" as the first element of your...
by faisal
Fri Feb 22, 2019 2:19 am
Forum: ChibiOS/RT
Topic: undefined reference to ST2MS and MS2ST
Replies: 21
Views: 3880

Re: undefined reference to ST2MS and MS2ST

Thank you again, you are all very supportive and really helping us to progress where our shortcomings fall Compiling: keyboards/cannonkeys/bluepill/ws2812.c keyboards/cannonkeys/bluepill/ws2812.c:49:3: error: initialization from incompatible pointer type [-Werror] PORT_WS2812, ^ keyboards/cannonkey...
by faisal
Fri Feb 22, 2019 12:33 am
Forum: ChibiOS/RT
Topic: undefined reference to ST2MS and MS2ST
Replies: 21
Views: 3880

Re: undefined reference to ST2MS and MS2ST

Oh yeah, QMK is cool. Rock on. :) Glad the project is moving to the latest release.
by faisal
Fri Feb 22, 2019 12:12 am
Forum: ChibiOS/RT
Topic: undefined reference to ST2MS and MS2ST
Replies: 21
Views: 3880

Re: undefined reference to ST2MS and MS2ST

Thank you for the reply that really helped we are also using your usb_driver files you made our version has some edits but is based on your 2016 version and since updating chibios and not this file it now gives the following error tmk_core/protocol/chibios/usb_driver.c:128:3: warning: initializatio...
by faisal
Wed Feb 20, 2019 8:49 pm
Forum: Development and Feedback
Topic: Internal Flash Driver
Replies: 27
Views: 5230

Re: Internal Flash Driver

Hello, Thanks for this flash driver for the L4 Is it possible for you to send a minimal example that use this library ? Thanks Alexandre Sorry, I don't have one at this time. It should be fairly simple to use - below is an example for erasing. STM32Flash flashDevBank2; stm32FlashObjectInit(&fla...
by faisal
Tue Feb 19, 2019 1:41 am
Forum: STM32 Support
Topic: Where to start STM32H7 support
Replies: 214
Views: 38856

Re: Where to start STM32H7 support

It should be replicable on an H7 nucleo board right? From your description, it seems that the problem is with the ChibiOS SPIv3 driver in DMA mode. Wish I had an H7 board lying around - would have tried it real quick for you. I know SPIv2 doesn't have this problem, I've used it on the L4, and F7.
by faisal
Tue Feb 19, 2019 1:04 am
Forum: STM32 Support
Topic: Where to start STM32H7 support
Replies: 214
Views: 38856

Re: Where to start STM32H7 support

Have you looked at the SPI bus on your saleae to confirm the extra byte being clocked? Is it real, or a software bug?
by faisal
Fri Feb 15, 2019 5:18 pm
Forum: Development and Feedback
Topic: Internal Flash Driver
Replies: 27
Views: 5230

Re: Internal Flash Driver

Giovanni, see the attachment. This should give you a head start. It's a working driver for the STM32L4 series based on the hal_flash abstraction.
by faisal
Tue Feb 12, 2019 11:09 pm
Forum: User Projects
Topic: stlink "clone" on stm32f042
Replies: 9
Views: 2881

Re: stlink "clone" on stm32f042

We actually use the stlink interface, through a debug handler (part of the Cortex3/4 debug support) with a chibios handler thread to communicate with our tags for configuration and control. We use google protocol buffers as the transport layer for RPC commands. Protocol Buffers ---> slink --> debug...

Go to advanced search