Hello,
We are three students in an Embedded Systems Course. We have been developing for 3 weeks on an ARM Cortex M0. We got started with the famous peripherals_example in order to understand and learn basic functions such as printf_string. This sample worked the first time, every display were correct, however now it doesn't seem to work any more. All we can see is a mix of weird characters (a picture here :http://imgur.com/2D2WPPh)
It might be bad a parameter to the hardware causing so much trouble for Tera Term to interpret data. Are you familiar with that kind of error ? Is there a way ? A button to press ? A memory address to configure ? To see properly what we wrote via printf_string function (which is exactly the same function dialog-semiconductor provides).
We are truly grateful of any answer that might help us to learn to develop for that kind of hardware.
Hello everybody,
We still don't produce anything more than these particular characters, even when trying to change some settings randomly like the Baud Rate and the configuration when uploading to flash.
I suggest for ourselves that we may read another useful document than what is shared on the Ressources tab. Can someone shared a theoretical pdf about exchange between a computer and a board through USB (data format, interface...).
Thanks in advance.
Hi There, you can find a few good threads on PRINT on the forum : these can be found by doing as search... (We are a bit short staffed right now due to Easter vacations and production support at customers). BR JE_Dialog.
http://support.dialog-semiconductor.com/printing-stuff
http://support.dialog-semiconductor.com/how-can-i-add-uartprintf-project-reporterfh-print-msg-debuging
Hello,
Thanks to link some threads related to print debug trace, however neither ramapra nor zqinglin seems to experience the same problem as us. In fact, we haven't found any related topics with obivous keywords such as "weird print", "unreadable character". Moreover, we really think it is not a problem of the printf_string() function, but a configuration when encoding and/or sending data through J-Link / J-Trace Cortex.
Unless there is a known issue in the sample code : peripherals_example, which I didn't read about, isn't there ?
As we are now aware of your short staffed period, we fully understand the delay of your answer.