)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"3fb2e32ba9b295a4213373a9edb6c1b642a55cf6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5548f5df_70231128","updated":"2024-07-14 15:27:01.000000000","message":"Paul,\nJenkins fails because the docker has no jimtcl installed.\n```\n./src/helper/jim-nvp.h:22:10: fatal error: jim.h: No such file or directory\n   22 | #include \u003cjim.h\u003e\n      |          ^~~~~~~\n```\n\nWould it be possible to install it?\n\nAnother point about the OpenOCD release. Should it include the jimtcl submodule? Or should it rely on jimtcl installed by the distro?","commit_id":"1f81ae7fd516d7ea6728bfe64040531ef485f9b2"},{"author":{"_account_id":1000160,"name":"Paul Fertser","email":"fercerpav@gmail.com","username":"pfertser"},"change_message_id":"089e6ad242dc5b420b0fbc820d7c5b6c58c20b9f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"6da2d222_2ad2dfb5","updated":"2024-11-16 14:36:25.000000000","message":"About jimtcl, yes, I think most major GNU/Linux distros won\u0027t even notice as they switched to external jim long time ago. About libjaylink they\u0027ll probably have to care but since we\u0027re early in the release stage (it\u0027s not officially started yet even) that should be fine too.\nGuess after this is merged a notification about the changes might be good to have on the mailing list, for the maintainers and those self-building from source code.","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"9349db6e4230a65bc05306c6ce37d7a0eb3fd920","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"0c5af02f_e53a06f7","updated":"2024-11-16 14:23:19.000000000","message":"I think this patch and the next are ready and jenkins has been updated to support them.\nPaul, is it ok?","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"d645df1f9869530f4b95b83fda0a85eb037bd8a7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"593a58a0_62bd2e71","updated":"2025-01-25 15:10:55.000000000","message":"Merge?","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"},{"author":{"_account_id":1002347,"name":"Richard Pasek","email":"rpasek@google.com","username":"rpasek"},"change_message_id":"1041b2d4840504d6ac34c528157b1e0722a004a8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"b7e059d5_852fa69e","in_reply_to":"0fc2cba6_539c65d0","updated":"2025-01-30 12:33:46.000000000","message":"Sorry for missing this before this merged. The deprecation of this makes it more difficult to build for Android.\n\nI\u0027ve been cross compiling for Android with \n```\nexport PKG_CONFIG_LIBDIR\u003d \u0026\u0026 export CC\u003d~/Downloads/android-ndk-r27c-linux/android-ndk-r27c/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android35-clang \u0026\u0026 ./configure --host\u003daarch64-clang-linux-android35\n```\n\nI\u0027m happy to see that I can still do this by using the `--enable-internal-jimtcl` flag.\n\nOne of my hopes with OpenOCD is to allow developers to debug sensor hub and other helper MCUs on Android devices. While I understand that removing jimtcl doesn\u0027t make this impossible, it does increase the barrier to entry for Android system developers.","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"},{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"73302225349b32d4fef1109c9cbaf4537ae766e4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"0fc2cba6_539c65d0","in_reply_to":"6da2d222_2ad2dfb5","updated":"2024-11-16 15:23:02.000000000","message":"\u003e Guess after this is merged a notification about the changes might be good to have on the mailing list, for the maintainers and those self-building from source code.\n\nI will merge this next weekend, then I will post on the mailing list\nThanks","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"},{"author":{"_account_id":1000853,"name":"zapb","display_name":"Marc Schink","email":"dev@zapb.de","username":"zapb"},"change_message_id":"ccd1a1bd240c2c41a9549c83fb6c9a0de4545474","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"e2fa779d_397372eb","in_reply_to":"b7e059d5_852fa69e","updated":"2025-01-30 22:12:40.000000000","message":"Nice to see that OpenOCD is used on Android for debugging! Is there more information that you can share? I guess the `linuxspi` adapter is part of your effort to use OpenOCD on Android devices?\n\nHow is your workflow? I worked with AOSP quite a while ago and it basically builds **everything** from source (with Bazel ;D). I assume it would be easy to additionally build libjim and OpenOCD?","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"},{"author":{"_account_id":1002347,"name":"Richard Pasek","email":"rpasek@google.com","username":"rpasek"},"change_message_id":"9606c5199b5d8977cf825608bc036e86c0670709","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"36c57925_d0c8555e","in_reply_to":"e2fa779d_397372eb","updated":"2025-02-01 02:57:35.000000000","message":"Yes exactly. linuxspi is my effort to make the periphery MCUs connected to the main SOC more debuggable.\n\nAOSP hasn\u0027t changed in this regard. Most things are still built from source. Machines have improved though so it\u0027s now possible to build it in about 45 minutes. While it\u0027s true that adding libjim and OpenOCD to the AOSP build would be fairly simple to do from a coding perspective, getting GPL 2 licensed projects into AOSP is a lengthy and difficult process.\n\nMy current plan is to have developers \n\n* Clone OpenOCD, \n* Cross compile it from source with the ADK, for example `export PKG_CONFIG_LIBDIR\u003d \u0026\u0026 export CC\u003d~/Downloads/android-ndk-r27c-linux/android-ndk-r27c/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android35-clang \u0026\u0026 ./configure --host\u003daarch64-clang-linux-android35 \u0026\u0026 make`\n* `adb push` it to device \n* Use `adb forward tcp:3333 tcp:3333` to allow the gdb instance on the host machine to access the OpenOCD instance running on device. \n\nHaving to cross compile libjim from source adds an additional point of failure. \n\nMy hope is to prove the usefulness of OpenOCD to decrease the barrier to entry either into AOSP or ADK. I\u0027d like to provide prebuilt OpenOCD binaries for Android but I\u0027m unclear where they\u0027d live outside at the moment.","commit_id":"b9cef6b89e4886069bea1ad35c754a8e53fb92f1"}]}