- Why are peripheral registers values not displayed ?
- Why are "No source file named ..." warnings displayed the debug console ?
- Why debug does not launch when my device is connected to USB 3.0 port ?
- Why can't I connect to the board, with error "Error in final launch sequence / Failed to execute MI command: / -target-select remote localhost:3333"
Peripherals registers cannot be displayed permanently because it would generate too much traffic on the debug link. Also, reading certain registers may have side effects (for UART reception registers for instance, the value may be lost after a read).
To see the values of a peripheral register, the register group it belongs to must be opened and the register must be selected by clicking on it.
The undue warning message is refering to sources from another project, it won't affect the debugging process. The IDE indexer is checking all the open projects and some functions name might be the same between project.
If you want the message not to be displayed, close the unrelated projects.
Some USB 3.0 Controllers (such as NEC/Renesas) has bug that prevents access to USB devices. Make sure to upgrade to the latest version of the controller driver to fix this issue.
For further information, please visit : https://github.com/libusb/libusb/wiki/Windows#usb-30-support
If you get this error, first check your USB cable; some cables, like those delivered with some USB chargers, will only transfer power, but not data.
Open the Windows device manager; if your cable is correct you shoud see your board appear as a STLink dongle (under Universal Serial Bus devices).
Depending on the board (Nucleo boards as well as recent disco or eval boards) you will also see a Mbed Microcontroller device appear under Disk Drives
If you don't see any of these, try another cable, as this may be the problem.
Newest Forum Posts
- Newbie trouble. Debug my own board via ST-LINK-V2 in Discovery, 2017-04-24 23:33
- Debugger becomes unresponsive when enabling SysTick interrupt, 2017-04-24 18:43
- Debugger becomes unresponsive when enabling SysTick interrupt, 2017-04-24 14:52
- Select MCU (TARGET), 2017-04-24 08:25
- AC6sw installing problem, 2017-04-23 19:30
- jtag status contains invalid mode value - communication failure, 2017-04-22 23:45
- Export a complete project, 2017-04-22 21:23
- Newbie trouble. Debug my own board via ST-LINK-V2 in Discovery, 2017-04-21 15:40
- Timer interrupt error., 2017-04-21 15:35
- Bootloader, linker and application start address, 2017-04-21 10:25