2024-04-04 09:56 AM
I just bought STM32 Discovery Board with STM32F407VGT6U ICs, the thing is i use the stm32duino extension on arduino IDE, and on one laptop we can't upload it, on other laptop the Board can't send Serial data, previously i use the STM32F407VET6 series and work just fine. also i hear that the 'U' at the end stand for the Java dedicated device? is it true? and can i make it like VGT6 basic series? also some people said you need to erase it to make it like normal, how to do it? Thank you, any help is appreciated
2024-04-04 10:04 AM - edited 2024-04-04 10:08 AM
The meanings of all the letters at the end of the part number are described in the Datasheet
2024-04-04 10:08 AM
No it's not Java. It means that it for development/education purposes, and is Unlicensed for commercial applications, so IP licenses related to CAN, Ethernet, etc have not be paid.
Basically ST paid less for the part in terms of internal accounting.
The U and Non-U part will be functionally the same. The VG vs VE is just the amount of FLASH tested on the die.
The amount of glare in the picture makes it practically unreadable. Use macro mode if available, and a closer / oblique angle to minimize glare.
2024-04-04 10:12 AM
This was the Java one STM32F407IGH6J
https://www.st.com/en/evaluation-tools/stm3240g-java.html
2024-04-04 10:19 AM
See also your previous thread: https://community.st.com/t5/stm32-mcus-products/what-the-difference-between-stm32f407vet6-and-stm32f407vgt6/td-p/655454
2024-04-04 11:01 AM
i still kinda confuse tho, maybe cause i use arduino IDE, but the Serial print not work there, works fine with older board VET series one, also when i plug it in, it appears like on the image here. it like it's acts like flashdisk or other save device
2024-04-04 11:04 AM
maybe you can explain it as i'm still confuse with this as it act like a save device
2024-04-04 12:11 PM
The STLink built in to the DK board should present BOTH the disk drive (which you can use to download firmware by drag-n-dropping the BIN (or hex) file onto the drive), and a virtual COM port.
When you say "the board can't send serial data" what exactly do you mean? Do you mean the STM32 firmware writes to the UART but the PC doesn't see it? Are you using the STLink virtual COM port for the serial data (i.e. using the STM32F407 UART that is connected to the STLink's UART)?
2024-04-04 12:21 PM
well there's some thing that i still confused for, first when plug there was appear a drive like it act as a flashdisk or something you can save file on it too (picture below), second when i plug the debugger (ST-LINK) it was recoqnised as COM PORT which my previous STM32 Discovery dev board not like that as the previous only the UART Serial one's recoqnised as the COM-PORT and not the debugger. maybe you can help me with it, sorry maybe i'm asking too much.
2024-04-04 03:17 PM
The ST-LINK/V2-1 implementation used for mBed provides a means to drag-n-drop .BIN files which will be burned onto the FLASH of the STM32. It also adds a VCP, but unfortunately on the STM32F407I-DISCO this doesn't connect to anything, as it's an older design originally shipping with ST-LINK/V2 implementation that lacked both of these additions.
On NUCLEO boards, and newer DISCO/DK boards, this VCP typically connects to a UART on the STM32, allowing for diagnostic or telemetry type output to be viewed on a terminal. This can aid debugging, provide dynamic analysis, or a means to communicate and configure your code from a PC.