2016-05-03 04:53 PM
2016-05-03 07:03 PM
What's the version number of the System Loader on the parts that fail? What date code/markings do the devices have?
Have you confirmed the HSE starts on the problem devices, how long from enable to ready?2016-05-03 07:11 PM
Hello clive1, thanks for reply.
Where may I see the version number of the System Loader ?? Do not understand what do you mean with date code/markings, if you mean all the references printed in chip, attached picture about one. About HSE if you mean the oscillator, tested with 10 boards, all work when upload firmware with ST-Link V2 programmer, only can not upload with BOOT DFU USB when board install a F427 MCU, because of Windows do not recognize it. But when board run firmware, USB work perfect, only DFU USB not recognized. ________________ Attachments : F427.jpg : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006I1LR&d=%2Fa%2F0X0000000bla%2FXcipkrXCUXo_9.T8XiCLyhsV2UrU1aS08IE3UN02gzQ&asPdf=false2016-05-04 03:00 AM
Review the documentation for the ROM based loader, there's a command to read the version.
That your code works via ST-LINK update really doesn't quantify the HSE start time or performance. You need to measure that start time and measure the frequency via the MCO pin. The System Loader is dependent on specific HSE performance for DFU/USB connectivity.2016-05-04 03:09 AM
2016-05-04 05:35 AM
You are using different firmware and silicon. USB operation is dependent on the correct measurement of the external clock source. HSE is benchmarked, and needs to be one of a short list of frequencies, per documentation.
You'd connect via USART1 or USART3, and send a couple of hex commands. Nominally 0x7F and then 0x01,0xFE, ie Get Version You could probably also download the ROM and pull the version bytes out of that. Perhaps you need to work through this with your ST FAE, or those of your distributor.2016-05-06 06:28 AM