Cautions

* Reset pin of MCU

Don't connect or disconnect easyDSP pod during MCU operation. It could cause any unintentional reset to MCU. In case you have to connect, please connect easyDSP to PC first, then to MCU. In case you have to disconnect, please disconnect easyDSP from MCU first, then from PC.
For your reference, reset signal is driven to low by easyDSP during 500msec. Therefore you can add enough filters to the reset pin of MCU.

* What is proper baud rate  ?

Normally higher baud rate means faster communication. But MCU should be able to handle this much high baud rate data communication. For example, it takes around 86usec (1/115200bps*10bit) for easyDSP to send one byte to MCU at 115200bps baud rate. MCU should process this one byte data within next 86usec for proper communication. If higher prioritized routine takes most of time and very small time is left for ISR routine for SCI, then easyDSP fails its communication and display the value of variables as '?'.

* Various IDE

For Arm MCU, easyDSP is designed for a wide range of software integrated development environments (IDEs) but is not fully tested for all IDEs. If not working properly, report it to easyDSP@gamil.com .

* Variable is not displayed

Depending of options of compiler and linker, the variable could be not displayed in the easyDSP if this variable is not used meaningfully in the user program.
This variable is not displayed in the map file too. Or displayed but with its address 0.
To display it in the easyDSP, please change the compiler/linker option accordingly.