-
Notifications
You must be signed in to change notification settings - Fork 8
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
Keil uVision 5.32 cannot handle some cprj files #11
Comments
Typo: issue with F4 |
When you try to (re-)create the project manually in MDK for the STM32F429ZITx device from scratch given your packs for the STM32F4 family, would you be able to see all the expected components in the RTE dialog and are you able to select them and have the sources added to the project? Please ensure that these are components with Cvendor="STMicroelectronics" and not "Keil". Are the "Keil" components present in your system? |
@jkrech I've encountered the same issue with a L5 STM32L562E-DK project. "Keil" package and components are also installed and present in the system ... not sure if this has an impact. When resolving manually dependencies and adding components in "Manage Run-Time Environment", the files are correctly added to the project. |
@jkrech Hi Joachim, good catch : you've got it right ! But...why is it so ? Thanks & Regards, |
Same here, by removing the Keil one, this works as expected ... |
Hi,
I am working with a STM32F7, F4 and L5.
With all of them I can create clayers and build successfully with cbuildgen make for my 3 IDEs : ac6, gcc, iar.
Then I try to open the cprj file with Keil uVision 5.32.
Everything goes fine for F7 and L5 but for F4 (jk: corrected) only the HAL EXTI driver file is present in the Device group.
Looking at the files I see no difference between a one which is working (F7) and one which is failing (F4).
In both cases the CMSIS packs for DFP and drivers are my STMicroelectronics one, prepared in the same way.
Would you possibly give me some hints to investigate this issue further ?
Thanks & Regards,
I2C_MasterTransmit_IT.zip
Fred
The text was updated successfully, but these errors were encountered: