Search found 13 matches
- Tue Oct 04, 2016 8:14 am
- Forum: Development of MicroPython
- Topic: USB HID OUT endpoint implementation
- Replies: 6
- Views: 6645
Re: USB HID OUT endpoint implementation
Merged to master in https://github.com/micropython/micropyt ... 21f017db29 and previous 3 commits. Thanks Philip!
- Thu Sep 22, 2016 7:46 pm
- Forum: Development of MicroPython
- Topic: USB HID OUT endpoint implementation
- Replies: 6
- Views: 6645
Re: USB HID OUT endpoint implementation
I was just implementing the same stuff today and went almost exactly the same path. Luckily I found your changes before I re-implemented them all. I took your changes, added a small fix on top and created a pull request: https://github.com/micropython/micropython/pull/2448
- Fri Apr 01, 2016 5:10 pm
- Forum: MicroPython pyboard
- Topic: Why is CCRAM not being used?
- Replies: 3
- Views: 3489
Re: Why is CCRAM not being used?
Ah, I see. I knew there must be something I am missing out.
- Fri Apr 01, 2016 4:41 pm
- Forum: MicroPython pyboard
- Topic: Why is CCRAM not being used?
- Replies: 3
- Views: 3489
Why is CCRAM not being used?
STM32F405 has RAM (128k) and CCRAM (64k). Currently the linker script for stm32f405.ld does not utilize CCRAM at all.
Why are we not using CCRAM at all? Can we use CCRAM for DATA and BSS (332+27620 bytes) for example (and having full 128k for python runtime)? If not, why?
Why are we not using CCRAM at all? Can we use CCRAM for DATA and BSS (332+27620 bytes) for example (and having full 128k for python runtime)? If not, why?
- Tue Mar 08, 2016 5:08 pm
- Forum: Development of MicroPython
- Topic: qstrdefs generator
- Replies: 11
- Views: 9583
Re: qstrdefs generator
I think we need to perform the full scan anyway, because the way it is handled now is that qdefs from multiple sources are being output to one file and this would break on parallel build. I think that it should be upto a port to specify which trees to scan. We probably shouldn't be scanning the cc3...
- Tue Mar 08, 2016 1:12 pm
- Forum: Development of MicroPython
- Topic: qstrdefs generator
- Replies: 11
- Views: 9583
Re: qstrdefs generator
So it seems like we all like approach b). Good. I think we need to perform the full scan anyway, because the way it is handled now is that qdefs from multiple sources are being output to one file and this would break on parallel build. I updated the script, so it performs a subdir scan for *.c if ar...
- Mon Mar 07, 2016 12:36 pm
- Forum: Programs, Libraries and Tools
- Topic: extmod generator
- Replies: 9
- Views: 9581
Re: extmod generator
I created a spin-off thread for this topic here: qstrdef-generatordhylands wrote:The issue I see with generating qstrdefs automtically is figuring out what #ifdefs they belong in. We don't want to include unnecessary qstrs in the image.
- Mon Mar 07, 2016 12:35 pm
- Forum: Development of MicroPython
- Topic: qstrdefs generator
- Replies: 11
- Views: 9583
qstrdefs generator
split-off conversation from extmod generator thread: The issue I see with generating qstrdefs automtically is figuring out what #ifdefs they belong in. We don't want to include unnecessary qstrs in the image. I see two approaches for achieving this: a) collect all qstrdefs and remember set of #if co...
- Fri Mar 04, 2016 12:09 am
- Forum: Programs, Libraries and Tools
- Topic: extmod generator
- Replies: 9
- Views: 9581
Re: extmod generator
No makeqstrdata takes the qstrs found in one of the qstrdefs.h files and generates the c structures associated with a qstr. Ah I see, implemented in 53ff05cd419ea37b128807effe833b480845fbaf I'd love to see a tool which created the qstrdefs.h file automagically, but it hasn't been written yet. Getti...
- Thu Mar 03, 2016 11:36 pm
- Forum: Programs, Libraries and Tools
- Topic: extmod generator
- Replies: 9
- Views: 9581
Re: extmod generator
- I think the convention in Python is generally to use __author__ instead of _author (and __version__, etc.) for module meta data. OK, changed in 409337515c0db6789a8344164102955b7ce0ce96. - Would be nice to generate the qstr definitions as well (maybe put them in a comment in the .c file). Aren't t...