1 2
1. GND
3. DC
7. Reset_N
CC2511 Dongle
2.VDD
4.DD
Figure 4: Recommended debug connector layout (Top view)
Figure 4 shows the required signal for a minimum connector layout.
Figure 5: SmartRF04EB debug connector for debugging
CC2511 Dongle / other external target systems
5.1Debugging USB firmware
When writing and debugging USB firmware one should remember that when Windows (or another OS) detects a USB device it will assume that it works in accordance with the USB specification. During debugging this might not be the case. Breakpoints may stop the execution of code on the CC2511 Dongle and firmware under development may not be completed or error free. This may lead to the PC disconnecting the CC2511 Dongle and turning off or toggling its power supply. In some cases Windows (or the OS in use) may crash or misbehave. Hence breakpoints should be used with caution.
Obviously inserting and using breakpoints in the firmware during debugging will be extremely useful to pinpoint bugs and follow code execution. And they can and should be used. But they will also stop the code execution on the CC2511 and may cause the device to act in conflict with the USB specification. This can lead to the PC disconnecting the CC2511 Dongle, sending a USB reset or worst case the operating system may crash.
If the firmware contain bugs that make the PC disconnect the CC2511 Dongle it may be necessary to disconnect the USB cable, and power the CC2511 Dongle from the SmartRF04EB in order to reprogram it.
SWRU082 | Page 7 of 24 |
