But I don’t know how can Babel is flashed with source code. source code have an IAR project file, so how do I build it and get the resulting file.
I made *.application.bin file to flash the Orel 20 through UAVCAN GUI Tool before. Like this, Is there any method to flash without using blackmagic probe? To do this I found a method to make binary file from EWARM. But I can’t sure of that. Is it right?
Greetings!
This project can be compiled in IAR v7.5 and later.
Unfortunatel IAR does not support DCP out of the box(but maybe there is a way to use it), so I had to flash babel with ordinar st-link. I had to make an adapter from that tiny DCP connector to ordinar 0.1’’ pitch PLS, which I the connected with my ST-LINK(this is a quection of 10 minutes though).
Anyway, I find it a bit tricky to use DCP in windows environment, so st-link is a good option.
You must also keep in mind that this project is just a demo, so feel free to copy bits of code to your IDE of choise, no need to use IAR only as it is definetly not free. Though, compiled project is under 16K of FLASH memory, so you can use free limited version of IAR to evaluate it. Find it here at the bottom of the page
As far as I know SWD interface is active after reset by default and you can only disable it in your program, so no, there is no need to add any code.
Can you please describe a bit more detailed what were your actions? Did you use IAR?
Ir seems everything should work.
Just for clarification:
to start debug session you need only 4 connections: GND, 3v3, SWDIO, SWCLK.
Are you sure BABEL is powered by st-link? Some programmers use VDD pin not to supply power, but to READ targer supply voltage to match logic levels.
Make sure you are powering BABEL with 3.3V
Also please try to connect to the MCU using STM32 ST-LINK Utility
This way we will figure out if the issue is with IAR or with wiring(or st-link)
Looks nice. Check couple mode things.
Try to connect to MCU but power BABEL from USB instead of st-link
Also your wires may be too long, it is sometimes an issue. Try slowing down SWD interface in STM32 ST-LINK Utility. Go to TARGER->SETTINGS and find it here
Yes, I meant just this. Power from usb and connecto only 3 pins (gns, swdio, swclk to ST-LINK).
If this also fails - inspect the debugging connector. Maybe it is defective or soldered badly?
I solved problem. Power from usb and connect only 3 pins (gnd, swdio, swclk to ST-LINK) as you said.
And also connect VCC to ST-LINK not VDD. Then it works!
Thanks!