Update VS Code launch config to debug on remote Tizen device#72318
Open
antonijakubiak-samsung wants to merge 12 commits into
Open
Update VS Code launch config to debug on remote Tizen device#72318antonijakubiak-samsung wants to merge 12 commits into
antonijakubiak-samsung wants to merge 12 commits into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the VS Code launch configuration for the Tizen LightingApp to target the aarch64 architecture, adjusting paths, debugger settings, and setup commands. Feedback on these changes suggests removing the SIGINT signal handling configuration, as it prevents the debugger from pausing execution, and removing the redundant set solib-absolute-prefix command since set sysroot is already defined.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #72318 +/- ##
==========================================
- Coverage 56.76% 56.76% -0.01%
==========================================
Files 1634 1634
Lines 112660 112660
Branches 13143 13143
==========================================
- Hits 63949 63948 -1
- Misses 48711 48712 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
PR #72318: Size comparison from 6d328aa to bee6d75 Full report (31 builds for bl602, bl616, bl702, bl702l, cc13x4_26x4, cc32xx, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
|
PR #72318: Size comparison from c55b996 to c100777 Full report (12 builds for cc13x4_26x4, cc32xx, nrfconnect, qpg, realtek, stm32)
|
|
PR #72318: Size comparison from c55b996 to c62792e Full report (35 builds for bl602, bl616, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
|
PR #72318: Size comparison from 92d95f2 to 33a7bc4 Full report (35 builds for bl602, bl616, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
enkiusz
requested changes
Jun 5, 2026
| // 2. /opt/bin/aarch64-linux-gnu-gdbserver :9999 --attach <PID> | ||
| // ========================================================================= | ||
|
|
||
| "cwd": "${workspaceFolder}/out/tizen-arm64-light-no-thread-no-ble", |
Contributor
There was a problem hiding this comment.
We need to stick to the generic application without Thread or BLE disabled.
Contributor
Author
There was a problem hiding this comment.
Both Thread and BLE are not working on Tizen 10 on Raspberry Pi 4 with the chip applications.
- Thread requires H/W and S/W
- BLE is not working
I think, we could modify thechipapplications for Tizen to detect BLE and Thread in runtime - however this should be a scope of a different task. So I prefer to keep the-no-thread-no-bleconfig, because it has a better chance to work. I was not able to simpy run BLE on Tizen, and the app withblecrashes on:
I/BT_FRWK_API(91575): bt-gatt-service.c: bluetooth_gatt_server_init(2718) > Sync Request => type=BT_BLUEZ_SERVICE, fn=BT_GATT_SERVER_REGISTER(0x1a4)
I/BT_FRWK_API(91575): bt-gatt-service.c: bluetooth_gatt_server_init(2723) > GATT Server Registration failed result [-11]
I/BT_FRWK_API(91575): bt-gatt-service.c: bluetooth_gatt_server_init(2733) > GATT Server instance ID obtained [-1]
E/CAPI_NETWORK_BLUETOOTH(91575): bluetooth-gatt.c: bt_gatt_server_initialize(2829) > DEVICE_NOT_ENABLED(0xfe400102)
E/CHIP (91575): DL: bt_gatt_server_initialize() failed: Operation failed
E/CHIP (91575): DL: BLEManager initialization failed: src/platform/Tizen/BLEManagerImpl.cpp:128: Platform Error 0xFE400104: Operation failed
I/CHIP (91575): -: Failed to init Linux App: src/platform/Tizen/BLEManagerImpl.cpp:128: Platform Error 0xFE400104: Operation failed
Contributor
There was a problem hiding this comment.
Ad 1. It does require HW/SW but the matter application detects this. Or at least it should, I have not tested thread on tizen at all tbh.
Ad 2. This PR can wait until we fix BLE on Tizen. It is much more important. If we change the config now to have -no-thread-no-ble and then fix BLE segfault then we will have to make a second PR to change it again. This is suboptimal.
Contributor
There was a problem hiding this comment.
I have just now read your log, DEVICE_NOT_ENABLED suggests that the bluetooth device is disabled in the OS (à la rfkill). If tizen apps crash with bluetooth disabled this needs to be fixed.
Contributor
Author
There was a problem hiding this comment.
BLE is fixed. #72666
Config is updated to no-thread only.
|
PR #72318: Size comparison from 527e5c9 to 9836b77 Full report (35 builds for bl602, bl616, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
|
PR #72318: Size comparison from 10dc250 to a0d4dac Full report (33 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
|
PR #72318: Size comparison from 7b11524 to 963d126 Full report (33 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32, telink)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update VS Code launch config to debug on remote Tizen device.
Set arch to 64 bit.
Testing
Run Tizen 10 on Raspberry Pi 4. Install
gdbserverCompile the
lighting-appfor Tizen, and install it on device withsdb.sdb shellSet VS code breakpoints on
void LightingManager::Set(bool aOn)Commission the
chip-tooland toggle lighing.Readability checklist
The checklist below will help the reviewer finish PR review in time and keep the
code readable:
descriptive
“When in Rome…”
rule (coding style)
See:
Pull Request Guidelines