Electronic – ST-LINK is serial communication possible

jtagmicrocontrollerstm32

I am using STM32F4 discovery board and Atollic TrueStudio for ARM Lite 3

I would like to pass some debugging data to PC using printf and I can't find a way to do it through STLink. Is it even possible? It seems essential feature for any debugging process.

Edit:
I need to use Serial Wire Viewer, but still no luck making it work.

Best Answer

OK, The way to achieve communication in Atollic TrueStudio for ARM Lite (yes it works under lite wersion since 3.0):

Enable Serial Wire Viewer in active debug configuration
Show SWV Console (under Debug prespective)
Open Serial Wire Viewer settings (first button in SWV Console window)
Enable ITM Stimulus Port 0
Enable Start/Stop Trace button in SWV Console (second button)
Use ITM_SendChar function
Enjoy debugging strings!

Related Solutions

Have to unplug the STM32F4 discovery card to update program

Wreck a $5 passive hub instead of a $500 computer!

Or find better upload tools...

If the newest release of the Atollic tools don't solve your problem, search "open source STM32 upload tool" - there may be an open source alternative, along the lines of "avrdude" for another family of CPUs.

You can still use the current tool chain for program development, as long as it can produce a standard executable format like ".elf" or Intel Hex, that the new uploader tool can recognize.

STM32F103 strange behavior

I may have figured this out. I have been using ST standard peripheral library to configure and use the SPI and DMA controllers (among others). I noticed that the SPI configuration registers were inconsistent depending on the declaration of variables at the start of main(). As an experiment I set the SPI config registers explicitly, eg as SPI1->CR1 = 0b0000100100110011. And everything works fine! I'm honestly still a bit confused as to why this might be a problem. I have been setting up the ST code as such: Under main() I declare

SPI_InitTypeDef     SPI_InitStructure;

Then further on down the track I initialise the SPI peripheral

SPI_I2S_DeInit(SPI1);
SPI_InitStructure.SPI_Direction = SPI_Direction_2Lines_FullDuplex;
SPI_InitStructure.SPI_Mode = SPI_Mode_Slave;
SPI_InitStructure.SPI_DataSize = SPI_DataSize_16b;  //SPI_DataSize_8b; 
SPI_InitStructure.SPI_CPOL = SPI_CPOL_High;                     // SCK idle high
SPI_InitStructure.SPI_CPHA = SPI_CPHA_2Edge;                    // second transition -> SCK Idle high => capture on rising edge of clock
SPI_InitStructure.SPI_NSS = SPI_NSS_Hard;                       // SS must be low during entire SPI transaction
SPI_InitStructure.SPI_FirstBit = SPI_FirstBit_MSB;                
SPI_Init(SPI1, &SPI_InitStructure);

But still there are shenanigans. Anyway, I will update if I make any more discoveries. I think I might abandon the ST peripheral library for initialisation, etc. Thanks again

Best Answer

Related Solutions

Have to unplug the STM32F4 discovery card to update program

STM32F103 strange behavior

Related Topic