{"id":8414,"date":"2023-09-20T21:50:44","date_gmt":"2023-09-21T04:50:44","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=8414"},"modified":"2023-09-20T21:55:10","modified_gmt":"2023-09-21T04:55:10","slug":"troubleshooting-keil-toolchain-issues","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/documentation\/toolchains\/keil\/","title":{"rendered":"Troubleshooting Keil Toolchain Issues"},"content":{"rendered":"

VisualGDB can automatically recognize the Keil ARMCC and ARMClang toolchains and import the installed device definitions from them:\"\"<\/a><\/p>\n

VisualGDB tries locating the toolchain by checking the HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Keil\\Products\\MDK\\Path<\/strong> value in the registry and then looking for the bin\\armcc.exe<\/strong> and bin\\armclang.exe<\/strong> files. This logic is defined in the %VISUALGDB_DIR%\\Rules\\KnownToolchains.xml<\/strong> file.<\/p>\n

If the automatic detection fails, you can simply click “Locate an IAR\/Keil toolchain manually” in the toolchain selector and point VisualGDB to the correct directory.<\/p>\n

Importing Keil Packs<\/h2>\n

VisualGDB will automatically locate and import the Keil packs (device definitions) in the following directories:<\/p>\n

    \n
  • <toolchain directory>\\pack<\/li>\n
  • %LOCALAPPDATA%\\Arm\\Packs<\/li>\n<\/ul>\n

    You can also specify additional directories to check for packs via Tools->Options->VisualGDB->Embedded->Keil->Extra pack directories<\/span><\/strong>.<\/p>\n

    Obtaining Diagnostic Logs<\/h2>\n

    If you do not see the Keil devices in the list, you can troubleshoot it by opening View->Other Windows->VisualGDB Diagnostics Console<\/strong>, enabling logging there, and clicking Tools->VisualGDB->Manage VisualGDB Packages <\/strong>to force VisualGDB to rescan all installed packages. Here is a sample output showing the package location:<\/p>\n

    Looking for Keil packages for e:\\Keil_v5\\ARM\\ARMCLANG...\r\nScanning e:\\Keil_v5\\ARM\\pack...\r\nFound 0 packages in e:\\Keil_v5\\ARM\\pack.\r\nScanning C:\\Users\\vmuser\\AppData\\Local\\Arm\\Packs...\r\nFound 10 packages in C:\\Users\\vmuser\\AppData\\Local\\Arm\\Packs.<\/pre>\n
    If the directories shown there don’t match the expected ones, or the log shows some exceptions, double-check all paths and permissions, and make sure VisualGDB can access the pack files.<\/p>\n","protected":false},"excerpt":{"rendered":"
    VisualGDB can automatically recognize the Keil ARMCC and ARMClang toolchains and import the installed device definitions from them: VisualGDB tries<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[202],"tags":[147],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/8414"}],"collection":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/comments?post=8414"}],"version-history":[{"count":1,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/8414\/revisions"}],"predecessor-version":[{"id":8416,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/8414\/revisions\/8416"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=8414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=8414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=8414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}