-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New board, same chip #19
Comments
Hi Richard,
Thanks for your interest! The "f40_41x" variant (which I used for the F405) may or may not be useful for the F407. |
Avik, Thanks. I'll follow the easy path for now and stay with a whole new variant. The menu idea sounds like a good way to go in the future. Once I've got most things working (SDIO,, the Winbond flash chip and the TFT interface will come a little later), I will create a pull request. Richard |
Avik, Are you going to use the AF columns for more than simply timer functions in the future? BTW: In the create a variant instructions, it would be worth adding that you have to edit the variant name in variant_codegen.py It took me a couple of goes, before I realised I was compiling code for another variant ('f446'). Also, as you're suggesting the f40_41x as a demo, it might be worth moving the ' "Teensy" Pin' column out of the way in that pin_map.csv file. All going well, now I've worked out the magic! Richard |
Avik, I've uploaded the current version of my Black VET6 variant to my repo https://github.com/palmerr23/BlackVET6_Koduino I've been working from Windows, so haven't recompiled the libraries yet (much easier on Linux!) I'm starting to work on the koduino ADC code for it, now that I've got most ADC functions working for the new "CUBE" code https://github.com/stm32duino/Arduino_Core_STM32F4. Which chip did you test the original ADC.c code with? Some of the defines look chip specific, for instance the following in stm32f4xx_adc.h are quite different from those for F407:
If I know which chip you started with, it will be easier to insert the conditional code to handle others. Richard |
Hi Richard, |
Hi Avik, The EXTSEL vaIues match exactly with those in your libraries. Problem solved. :-) Once I get the first test working, the rest (borrowed from STM32Cube_FW_F4_V1.16.0\Projects\STM324x9I_EVAL\Examples\ADC) should follow quickly, if my experience with getting them working for the new STM32DUINO/F4 code is any guide. Richard |
Avik,
There's been a lot of fun tying down specs for what's becoming commonly known as the Black F407VET6 board across the various STM32 Arduino cores - the Maple-based one that Roger has been looking after, the new STM32DUINO (Freceric Pillon) and DanielEff's GenericSTM32.
While I've successfully tested many functions with koduino, there are a few port assignments mandated by onboard hardware.
I'd like to generate a variant for koduino and have already made some solid progress.
A few questions:
Are you open to specific board variants - only different in pin configs? I get the feel that your main focus for now is on chip-level variations.
Have you done away with Arduino-style pin numbering altogether? (That is being able to use something that equates to a board header pin as well as the PortPin notation) Variant_codegen.py seems to always output data in alpha-numeric order, no matter what order the data is in. Maybe I've missed something in the pin_map.csv file layout.
Thanks in anticipation.
Richard
The text was updated successfully, but these errors were encountered: