Search Results

Quote from SEGGER - Nino: “Hello, We have a model overview on our website comparing each model to each other: segger.com/products/debug-prob…nk/models/model-overview/ More information about the individual model (electric characteristics etc.) can be found if you click on one of the model names. Is that what you were looking for? ” It sounded like the limitation was due to the debug controller on the target system rather than the external debug adapter. If this is the case, the maximum data trans…

Quote from SEGGER - Nino: “Hello, 1: The values from the Website are measured when a continuous data stream is transferred. Periodic "burst" transfers like in your setup might reach lower values. SWD is expected to be significantly lower due to larger overhead in the SWD protocol. We recommend using JTAG here. In theory the speed should go up linearly with the interface speed, unfortunately at some point the debug controller on the target device is not fast enough to respond to J-Link requests s…

Quote from SEGGER - Nino: “Hello, Thank you for your inquiry. 1: See "Transfer Speed" segger.com/products/debug-prob…about-real-time-transfer/ 2: Could you elaborate what you mean by RTT TCP/IP? 3: RTT was programmed with maximum performace in mind, so no automatic overflow detection implemented. You could implement int by validating the SEGGER_RTT_Write() return value. Depending on what you want to achieve you can also switch the operating mode. More information can be found in the J-Link user …

I recently started working with RTT and with the GDB servers SWO output functionality, and I have a few questions. 1. What data transfer rate can I expect using RTT and different interfaces (JTAG, SWD)? On my target (Cortex-M4, 96 MHz CPU clock), RTT transfer rate seems to top out at about 80 kb/s when using SWD, regardless of whether the SWD clock is 10 MHz or 25 MHz. With JTAG, the transfer rate can be as high as 300 kb/s at 25 MHz JTAG clock before data loss occurs. Is it normal that throughp…

I find this advertisement popup highly annoying and unprofessional. And yes, it's not a warning, it's pure advertising in the way it is presented. "Buy more stuff, or we'll annoy you with this popup every day until you do!"

Hello, I have run into a problem running an AT91SAM7S with a 24 MHz external clock, and think that I have narrowed it down to being an emulator-related problem, since the same code runs fine when it is running from flash without the emulator attached. The problem occurs when selecting the Main clock as the Master Clock. The processor seems to go into an undefined state and hangs (sometimes with an abort condition or other exceptions). However, if I set a breakpoint at the line where the switch o…