It would be really interesting to know why Keil omitted driver for SPI4 in their BSP software pack for STM32F4 family - SPI1, SPI2, SPI3 and SPI5 are supported, but SPI4 (and SPI6, for that matter) are not... Not to mention wrong DMA channel assignments for SPI2. I mean, it's not a problem to fix such things, but then new release comes out and you can't just upgrade, since bugs might not be fixed and you have to do it all over again. Pretty lousy work...
Better yet, fix the problems as you see them, and submit a complete patch with your report.
What???
But that would require thought and a degree of commitment. Two qualities that appear to be disappearing.
Keil are by no means alone in having problems in some of the source code they supply.
Just yesterday, a colleague downloaded some source code from Microchip. Compilation threw up a number of rather obvious minor errors. I saw it and determined that it would have been easy to at least get past the first hurdle.
Did my colleague attempt to fix it? Nope. he just swore, whinged, dumped it and then downloaded something from another site.
Anyone know someone who is looking for a firmware writer that is prepared to take time to think about a problem?
Yes, and isn't a great deal of software coded without direct access to hardware, in all possible permutations. Sometimes you're just given a specification and told to make it happen.
How many halfwits have we seen here complaining that something compiles and links without error, but then fails to actually work, as if the syntax checker can diagnose programming errors.
Submit a bug report to support, and move along. Better yet, fix the problems as you see them, and submit a complete patch with your report.
... whose name is in the copyright notice?
still bugs that make it clear nobody tested it for real at all - like wrongly assigned DMA channels, for example did you get it from Keil or ST?
Let's make things clear - in RTE there's a single SPI driver file that contains instances for SPI1, SPI2, SPI3 and SPI5. Even if you consider it as a separate driver for each SPI interface, there are still bugs that make it clear nobody tested it for real at all - like wrongly assigned DMA channels, for example... Anyway - over and out.
Well, "It would be really interesting to know why Keil omitted driver for SPI4..." certainly sounds like a complaint about a missing driver to me!
I am not complaining about missing drivers - I am complaining about poorly written ones. If they decided to release a driver, somebody should at least check for formal errors...
this issue is kind of moot due to the afct that manufacturers updts are notoriasly slow getting into the Keil directories.
when using device specifi code ALWAYS get it from the manufacturers website
Erik
PS not a big blame to Keil, keeping up with every manufactutrers upgrades (often no message "xx is updated" is sent) would be a herculean task
RTE version is 1.07, but SPI_STM32F4XX version is 1.04. And it is definitely not fixed.
Hello Dejan, which version of the STM32F4xx_DFP are you using (check the Pack Installer)? 1.0.7 should fix the problems you referred to.
Matthias
It would probably be more efficient to contact Keil support.
View all questions in Keil forum