Search Results

Hi Fabian, Thank you for looking into this. Yes, the suggested change to ensure the full 24 byte ID string is valid in the RTT control block fixes my issue. It does seem a bit strange to me that manual specification of the control block doesn't appear to check for the full ID string as does the automatic and search range options. I have some notes/suggestions for you to consider related to RTT improvements: - The information at wiki.segger.com/RTT#Memory_footprint could be updated to note the ex…

Hi Fabian, Just following up to see if you have made any progress on this issue? Given that the issue is reproducible, would you prefer I track this as a separate support ticket via segger.com/support/technical-support/? Thank you Austin

Hi Fabian, Thank you for your response. Your sample hex file works correctly on my hardware with the RTT viewer automatically detecting the control block and outputting 'Hello World xx!' with incrementing xx. With my original application programmed, I turned on the J-Link log file and captured an unsuccessful RTT attempt with auto-detection enabled, log is attached. The log includes a connection using auto detection (fail) and then connection using specified address (pass). A side issue I found …

Hello, I'm having an issue with the JLink not being able to automatically detect the RTT control block. If I set an exact control block address in J-Link RTT Viewer, the control block is located and RTT log output is as expected. If I set a search range which includes the known RTT control block address, the RTT control block is not found. Similarly, automatic detection does not locate the control block. My setup is as follows: Device: STM32F746IG. Linker specifies internal RAM @ 0x20000000, len…

Thanks Niklas. I retried my setup with mass storage disabled on my JLink OB and was able to successfully communicate using the VCP. You may want to update your wiki page to note that this problem affects Linux systems as well as OS X. Regards Austin

Can any one from Segger provide insight into this issue? I read the detail of wiki.segger.com/index.php?title=J-Link-OB_SAM3U which I think is likely to be the same issue. This page describes the problem from OS X but the details seem very similar to the problem that I'm seeing under Linux. I'd be interested to know if anyone else has come across this issue or can otherwise confirm that nRF52 DK virtual serial port works correctly under linux when using a USB High Speed connection. As per the me…

Hello, I'm having some issues getting the virtual com port (VCP) working correctly for a Segger J-Link OB connection to a Nordic nRF52840 Preview DK (nordicsemi.com/eng/Products/nRF52840-Preview-DK). When connected to the target board using Putty on Windows 10, UART comms via the VCP work correctly when JLink enumerates as a USB high speed device. When connected to the target board using Minicom or similar within Linux, UART comms via the VCP don't work if the JLink enumerates as a USB high spee…