Home
last modified time | relevance | path

Searched refs:debug (Results 1 – 25 of 52) sorted by relevance

123

/btstack/port/renesas-tb-s1ja-cc256x/template/btstack_example/.settings/
H A Dorg.eclipse.cdt.managedbuilder.core.prefs2 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
3 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
4 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
5 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
6 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
7 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
8 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
9 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
10 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
11 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/…
H A De2studio_project.prefs3 activeConfiguration=com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955
H A Dorg.eclipse.cdt.core.prefs2 environment/project/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/SECURE_BUILD_COM…
3 environment/project/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/SECURE_BUILD_COM…
4 environment/project/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/SECURE_BUILD_COM…
5 environment/project/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/append=true
6 environment/project/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.605996955/appendContribute…
/btstack/port/renesas-ek-ra6m4a-da14531/e2-project/.settings/
H A Dorg.eclipse.cdt.managedbuilder.core.prefs2 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
3 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
4 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
5 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
6 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
7 environment/buildEnvironmentInclude/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
8 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
9 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
10 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
11 environment/buildEnvironmentLibrary/com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467…
H A De2studio_project.prefs3 activeConfiguration=com.renesas.cdt.managedbuild.gnuarm.config.elf.debug.1416900467
/btstack/3rd-party/lwip/core/src/include/lwip/
H A Ddebug.h143 #define LWIP_DEBUGF(debug, message) do { \ argument
145 ((debug) & LWIP_DBG_ON) && \
146 ((debug) & LWIP_DBG_TYPES_ON) && \
147 … ((s16_t)((debug) & LWIP_DBG_MASK_LEVEL) >= LWIP_DBG_MIN_LEVEL)) { \
149 if ((debug) & LWIP_DBG_HALT) { \
156 #define LWIP_DEBUGF(debug, message) argument
H A Dip_addr.h233 #define ip_addr_debug_print(debug, ipaddr) do { if(IP_IS_V6(ipaddr)) { \ argument
234 ip6_addr_debug_print(debug, ip_2_ip6(ipaddr)); } else { \
235 ip4_addr_debug_print(debug, ip_2_ip4(ipaddr)); }}while(0)
236 #define ip_addr_debug_print_val(debug, ipaddr) do { if(IP_IS_V6_VAL(ipaddr)) { \ argument
237 ip6_addr_debug_print_val(debug, *ip_2_ip6(&(ipaddr))); } else { \
238 ip4_addr_debug_print_val(debug, *ip_2_ip4(&(ipaddr))); }}while(0)
306 #define ip_addr_debug_print(debug, ipaddr) ip4_addr_debug_print(debug, ipaddr) argument
307 #define ip_addr_debug_print_val(debug, ipaddr) ip4_addr_debug_print_val(debug, ipaddr) argument
354 #define ip_addr_debug_print(debug, ipaddr) ip6_addr_debug_print(debug, ipaddr) argument
355 #define ip_addr_debug_print_val(debug, ipaddr) ip6_addr_debug_print_val(debug, ipaddr) argument
H A Dip4_addr.h160 #define ip4_addr_debug_print_parts(debug, a, b, c, d) \ argument
161 LWIP_DEBUGF(debug, ("%" U16_F ".%" U16_F ".%" U16_F ".%" U16_F, a, b, c, d))
162 #define ip4_addr_debug_print(debug, ipaddr) \ argument
163 ip4_addr_debug_print_parts(debug, \
168 #define ip4_addr_debug_print_val(debug, ipaddr) \ argument
169 ip4_addr_debug_print_parts(debug, \
H A Dip6_addr.h313 #define ip6_addr_debug_print_parts(debug, a, b, c, d, e, f, g, h) \ argument
314 …LWIP_DEBUGF(debug, ("%" X16_F ":%" X16_F ":%" X16_F ":%" X16_F ":%" X16_F ":%" X16_F ":%" X16_F ":…
316 #define ip6_addr_debug_print(debug, ipaddr) \ argument
317 ip6_addr_debug_print_parts(debug, \
326 #define ip6_addr_debug_print_val(debug, ipaddr) \ argument
327 ip6_addr_debug_print_parts(debug, \
/btstack/port/stm32-wb55xx-nucleo-freertos/
H A DREADME.md20 The debug output is sent over USART1 and is available via the ST-Link v2.
32 The debug output is sent over USART1 and is available via PB6.
56 - example.elf: .elf file with all debug information
61 …debug the Nucleo68 board. The Nucleo68 boards comes with an on-board [ST-Link programmer and debug…
69 …er or after installing J-Link OB on the Nucleo68 board, you can flash and debug using the cross-pl…
71 …bug file in the build folder. When compiled with "ENABLE_SEGGER_RTT", the debug output shows up in…
75 All debug output can be either send via SEGGER RTT or via USART1. To get the console from USART1, s…
77 …h resp. in example/btstack_config.h of the generated projects, additional debug information can be…
/btstack/port/stm32-l073rz-nucleo-em9304/
H A DREADME.md25 - example.elf: .elf file with all debug information
28 …debug the F4 Discovery board. The F4 Discovery boards comes with an on-board [ST-Link programmer a…
32 …r after installing J-Link OB on the F4 Discovery board, you can flash and debug using the cross-pl…
34 …bug file in the build folder. When compiled with "ENABLE_SEGGER_RTT", the debug output shows up in…
38 All debug output can be either send via SEGGER RTT or via USART2. To get the console from USART2, c…
40 …h resp. in example/btstack_config.h of the generated projects, additional debug information can be…
/btstack/port/stm32-f4discovery-usb/
H A DREADME.md25 - example.elf: .elf file with all debug information
28 …debug the F4 Discovery board. The F4 Discovery boards comes with an on-board [ST-Link programmer a…
32 …r after installing J-Link OB on the F4 Discovery board, you can flash and debug using the cross-pl…
34 …bug file in the build folder. When compiled with "ENABLE_SEGGER_RTT", the debug output shows up in…
39 The debug output can send via SEGGER RTT.
41 …h resp. in example/btstack_config.h of the generated projects, additional debug information can be…
/btstack/port/stm32-f4discovery-cc256x/
H A DREADME.md30 - example.elf: .elf file with all debug information
33 …debug the F4 Discovery board. The F4 Discovery boards comes with an on-board [ST-Link programmer a…
37 …r after installing J-Link OB on the F4 Discovery board, you can flash and debug using the cross-pl…
39 …bug file in the build folder. When compiled with "ENABLE_SEGGER_RTT", the debug output shows up in…
44 All debug output can be either send via SEGGER RTT or via USART2. To get the console from USART2, c…
46 …h resp. in example/btstack_config.h of the generated projects, additional debug information can be…
/btstack/port/msp432p401lp-cc256x/
H A DREADME.md42 - example.elf: .elf file with all debug information
45 There are different options to flash and debug the MSP432P401R LaunchPad. If all but the jumpers fo…
49 When using an external J-Link programmer, you can flash and debug using the cross-platform [SEGGER …
51 …bug file in the build folder. When compiled with `ENABLE_SEGGER_RTT`, the debug output shows up in…
56 All debug output is send via SEGGER RTT or via USART2. To get the console from USART2, remove `ENAB…
58 In btstack_config.h resp. in example/btstack_config.h of the generated projects, additional debug i…
/btstack/port/archive/pic32-harmony/
H A DREADME.md9 was used for the debug output. Please remove the DAC board and connect a
10 3.3V USB-2-UART converter to GND and TX to get the debug output.
/btstack/3rd-party/
H A DREADME.md14 …debug-probes/j-link/technology/about-real-time-transfer/) | V786a | BSD 3-Clause | HC…
/btstack/port/renesas-tb-s1ja-cc256x/
H A DREADME.md61 In Ozone, the debug output is readily available in the terminal. A .jdebug file is provided in the …
66 All debug output is send via SEGGER RTT.
68 …h resp. in example/btstack_config.h of the generated projects, additional debug information can be…
/btstack/port/archive/pic32-harmony/app.X/
H A D.gitignore2 debug/
/btstack/port/posix-h4-bcm/
H A D.gitignore1 cmake-build-debug
/btstack/test/fuzz/
H A D.gitignore2 cmake-build-debug
/btstack/port/renesas-ek-ra6m4a-da14531/
H A DREADME.md86 This will build all examples as .elf files as well as .jdebug Ozone debug project files
94 Start Ozone and open the provided .jdebug file. The debug output is readily available in the RTT Te…
99 All debug output is send via SEGGER RTT.
/btstack/port/stm32-l476rg-nucleo-sx1280/
H A DREADME.md21 SEGGER RTT is used for debug output, so a Segger J-Link programmer is required, but the on-board
23 [SEGGER J-Link OB](https://www.segger.com/products/debug-probes/j-link/models/other-j-links/st-link…
/btstack/port/qt-usb/
H A D.gitignore25 *.debug
/btstack/port/qt-h4/
H A D.gitignore25 *.debug
/btstack/port/zephyr/
H A DREADME.md64 Using the nRF5340-DK for example allows debug output on both cores to separate UART ports.
73 with debug:

123