Search found 33 matches

by e_l_tang
Wed May 02, 2018 8:36 am
Forum: Development and Feedback
Topic: [NEW] Portable multi-device/board ChibiOS applications
Replies: 21
Views: 2258

Re: [NEW] Portable multi-device/board ChibiOS applications

Hi Theo. Moving to GitHub has a lot of benefits. GitHub has a lot more traffic and is familiar to a lot more people than this forum, so the likelihood of contributions there is much higher. Reviewing PRs and requesting changes to them is a really streamlined process, and all discussions remain easil...
by e_l_tang
Wed Apr 25, 2018 5:09 am
Forum: Development and Feedback
Topic: [NEW] Portable multi-device/board ChibiOS applications
Replies: 21
Views: 2258

Re: [NEW] Portable multi-device/board ChibiOS applications

Would it be possible for the AVR code to be moved over to the community repo like the Kinetis code was? I'm probably going to start sending some patches in the next few days and that would make it a lot easier for me.
by e_l_tang
Sun Sep 17, 2017 6:27 am
Forum: Development and Feedback
Topic: [NEW] Portable multi-device/board ChibiOS applications
Replies: 21
Views: 2258

Re: [NEW] Portable multi-device/board ChibiOS applications

I'd to suggest that a list be made of what still remains to be done in each port. Currently the only way to find out this information is reading the code or asking someone who is familiar with it, and I feel that this forms a barrier to people making contributions in their free time. I for one will ...
by e_l_tang
Thu Sep 14, 2017 7:47 am
Forum: Development and Feedback
Topic: [NEW] Portable multi-device/board ChibiOS applications
Replies: 21
Views: 2258

Re: [NEW] Portable multi-device/board ChibiOS applications

It was missing support for PAL lines, but I saw that Theo addressed that today. Currently it's missing an implementation of the newly added usbWakeupHost. There may be more things I'm unaware of.
by e_l_tang
Thu Sep 14, 2017 12:41 am
Forum: Development and Feedback
Topic: [NEW] Portable multi-device/board ChibiOS applications
Replies: 21
Views: 2258

Re: [NEW] Portable multi-device/board ChibiOS applications

I noticed that some of the AVR implementations of HAL drivers are not as complete as their STM32 counterparts. Does this mean that an STM32 project might need to be modified to work with AVR even though it doesn't use any drivers which aren't implemented on AVR?
by e_l_tang
Mon Sep 11, 2017 10:44 pm
Forum: AVR Support
Topic: New Makefile Topic is solved
Replies: 35
Views: 2373

Re: New Makefile Topic is solved

So far my preferred method for building AVR projects has been to use DMBS. There is a good summary of DMBS on its GitHub page . It's a very different way of using make and I'm not sure how well it would work with the existing ChibiOS build system, but I thought I'd mention it just so everyone knows ...
by e_l_tang
Sat Sep 09, 2017 4:25 pm
Forum: Bug Reports
Topic: Default USB request handler incomplete Topic is solved
Replies: 5
Views: 859

Re: Default USB request handler incomplete Topic is solved

Thanks for the quick turnaround.
by e_l_tang
Sat Sep 09, 2017 4:23 pm
Forum: Small Change Requests
Topic: Waking host with USB driver Topic is solved
Replies: 10
Views: 1250

Re: Waking host with USB driver Topic is solved

I took a look at the code and I think the high level driver could be made more general. On AVR the software simply sets the bit and the hardware takes care of the rest. It is not necessary for it to wait or clear the bit.
by e_l_tang
Thu Sep 07, 2017 12:10 pm
Forum: Bug Reports
Topic: Default USB request handler incomplete Topic is solved
Replies: 5
Views: 859

Re: Default USB request handler incomplete Topic is solved

All USB stacks I've encountered so far provide handling of this kind of request. Is there any reason why a Get Descriptor request would need to be handled outside of get_descriptor_cb?
by e_l_tang
Thu Sep 07, 2017 1:19 am
Forum: Bug Reports
Topic: Default USB request handler incomplete Topic is solved
Replies: 5
Views: 859

Default USB request handler incomplete Topic is solved

I found that Get Descriptor requests with interface recipients will not be handled correctly. Such a request will not cause the expected invocation of get_descriptor_cb.

Go to advanced search