So I just installed v4.19.0 and now at the Nucleo-F767ZI is missing from the Boards List. (Just F746ZG and F722ZE are there.) Prior to the install it was there and kinda worked but now it's not on the list.
What am I doing wrong?
Hello phroggie and Nicolas HILAIRE,
Just for your information, if you want to work with F767ZITx board before the next CubeMX release (CubeMx 4.20), the workaround is as follow :
Change in A_ST_Nucleo144BoardsList.pdsc, this part of code :
<mountedDevice Dname="STM32F767ZITx " Dvendor="STMicroelectronics:13" deviceIndex="0"/>
by this one :
<mountedDevice Dname="STM32F767ZITx" Dvendor="STMicroelectronics:13" deviceIndex="0"/>
(no space at the end of the Dname).
I will share internally your feedback for further review and we will keep you posted about the taken actions/explanation if needed.
Thank you for your contribution and we apologize for the inconvenience this may cause.
I have the same issue.
I have that the board is described in the database but doesn't appear under the software
<board name="NUCLEO-F767ZI" orderForm="https://my.st.com/esample/app?page=basket&pn=NUCLEO-F767ZI" revision="Rev.B" salesContact="http://www.st.com/stonline/contactus/contacts/index.php" vendor="STMicroelectronics" mxFile="boards/A71_Nucleo_NUCLEO-F767ZI_STM32F767ZI_Board.ioc" ARMmbed="" type="Nucleo144"> <description>STMicroelectronics NUCLEO-F767ZI Board Support and Examples</description> <image large="images/nucleo_144_large.jpg" small="images/nucleo_144_small.jpg"/> <book category="overview" name="http://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mcu-eval-tools/stm32-mcu-eval-tools/stm32-mcu-nucleo/nucleo-f767zi.html" title="Nucleo STM32 F7 series development board"/> <book category="manual" name="http://www.st.com/content/ccc/resource/technical/document/user_manual/group0/26/49/90/2e/33/0d/4a/da/DM00244518/files/DM00244518.pdf/jcr:content/translations/en.DM00244518.pdf" title="User Manual"/> <mountedDevice Dname="STM32F767ZITx " Dvendor="STMicroelectronics:13" deviceIndex="0"/> <compatibleDevice DsubFamily="STM32F767" Dvendor="STMicroelectronics:13" deviceIndex="0"/> <feature n="1" name="On-board ST-LINK/V2-1" type="ODbg"/> <feature n="4" name="USB VBUS, ext. VIN, ext. 5V, ext +3.3V" type="PWR"/> <feature n="1" name="10/100M Ethernet interface with external PHY (LAN8742A-CZ-TR)" type="ETH"/> <feature n="1" name="USB FS (Full speed) with micro-AB Connector" type="USB"/> <feature n="76" name="STMicroelectronics Morpho connector : (2 x 72)" type="DIO"/> <feature n="32" name="STMicroelectronics Zio (Arduino connector)" type="DIO"/> <feature n="2" u="1" name="Push-buttons: User and Reset" type="Button"/> <feature n="3" u="1" name="LEDs: COM, Power, User LEDs" type="LED"/> <debugInterface adapter="ST-Link" connector="Mini-USB"/> </board>
But in the model there is a path to the empty model.
I took this file and save this model as my working copy.
My path is : C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeMX\db\plugins\boardmanager\boards/A71_Nucleo_NUCLEO-F767ZI_STM32F767ZI_Board.ioc
I haven't finish my tests but it seems to be okay.
Hope it can help
Thank you so much, Nicolas.
However I'm missing something from your solution.
I found the code you outlined in the A_ST_Nucleo144BoardsList.pdsc file. The <board> element for the F767ZI board corresponds to the one for the F746ZG (for instance) and their mxFile attributes reference similar .ioc files in the boards folder (which it refers to with a relative path), both of which are present.
Was your solution to change that to an absolute path?
No when I saw the model file (.ioc), I just open it and save it under my working copy.
I'm not creating project from scratch be from their ico file.
For my board there is two files :
* A71_Nucleo_NUCLEO-F767ZI_STM32F767ZI_Board_all config.ioc (or something like that)
Take the second because all IP have already been configured.
After some tests it works perfectly.
Hello phroggie / Nicolas HILAIRE,
The issue is confirmed using STM32CUBEMX 4.19. and will be resolved and delivered in the next CubeMX release (CubeMX4.20).
Sorry for any inconvenience this may have caused.
The workaround works like a charm.
Thanks Eric and to everyone else who helped out!!!!!!!
Retrieving data ...