Important changes to questions
We’re making some changes to Mbed Questions. From 10th December 2019 this site will be archived and new questions should be asked on our new forum site. Until that date you can continue to reply to existing questions here but can’t ask new questions.
4 years, 12 months ago.
ST Link and custom board(Nucleo STM32L053)
I bought Nucleo STM32L053 board and started programming it with mbed. I tested my board with the already uploaded projects(Blinky, Hello World, etc.). Everything was ok. However, I have to carry out some experiments at the temperature above 50°C, which seems to be too much for Nucleo. So, I designed and ordered my own PCB with the same microcontroller and decided to debug my board with STLink(using mbed libraries). I simply looked at the Nucleo scheme and connected SWD signals, Rx and Tx from STLink to the same pins in the microcontroller(which is advised in the Nucleo manual). I removed CN2 jumpers and desoldered SB12 solder bridge. The same with GND and power supply. I left only Boot0 floating(mistake?) and there is no MCO signal on my board.
To load the flash memory, I used STLink Utility and according to command prompt, everything is ok. Utility verifies the software and everything seems to be correct. I could flash binary, 'Nucleo' drive is displayed as a drive in Computer folder and I can drag and drop there binaries. However, I don't get any message over COM port(TeraTerm), which I always had with Nucleo.
I read related topics, which had been posted here: https://developer.mbed.org/questions/3811/Prototype-to-Hardware-with-Nucleo/ http://developer.mbed.org/users/chris/notebook/prototype-to-hardware/ https://developer.mbed.org/forum/electronics/topic/5184/?page=1#comment-25504
Unofortunately, I didn't find any solution to my problem. Is there anyone, who encountered similar problem? Are BOOT0 and MCO necessary?
I'd appreciate any advice,
You need to log in to post a question