{"action":"created","issue":{"url":"https://api.github.com/repos/ARMmbed/mbed-os/issues/3174","repository_url":"https://api.github.com/repos/ARMmbed/mbed-os","labels_url":"https://api.github.com/repos/ARMmbed/mbed-os/issues/3174/labels{/name}","comments_url":"https://api.github.com/repos/ARMmbed/mbed-os/issues/3174/comments","events_url":"https://api.github.com/repos/ARMmbed/mbed-os/issues/3174/events","html_url":"https://github.com/ARMmbed/mbed-os/issues/3174","id":186428025,"number":3174,"title":"Confusing \"Target not supported\" errors from absent device_name field in targets.json","user":{"login":"sarahmarshy","id":12565767,"avatar_url":"https://avatars.githubusercontent.com/u/12565767?v=3","gravatar_id":"","url":"https://api.github.com/users/sarahmarshy","html_url":"https://github.com/sarahmarshy","followers_url":"https://api.github.com/users/sarahmarshy/followers","following_url":"https://api.github.com/users/sarahmarshy/following{/other_user}","gists_url":"https://api.github.com/users/sarahmarshy/gists{/gist_id}","starred_url":"https://api.github.com/users/sarahmarshy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sarahmarshy/subscriptions","organizations_url":"https://api.github.com/users/sarahmarshy/orgs","repos_url":"https://api.github.com/users/sarahmarshy/repos","events_url":"https://api.github.com/users/sarahmarshy/events{/privacy}","received_events_url":"https://api.github.com/users/sarahmarshy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-10-31T23:30:01Z","updated_at":"2016-11-02T11:28:51Z","closed_at":null,"body":"Since #3173 is the first time it has come up since #2708, but is likely to cause confustion again:\r\n\r\nIt's obvious that this type of solution needs to be clearer when a user gets a \"Target not supported\" error. \"Target not supported\" is potentially ambiguous, as it might mean that the target simply doesn't have a device name, but is described by some CMSIS pack. Though, it could be true that the device is not described in a CMSIS pack (would require user/vendor to manually check?). This will be more of a problem for release 2 targets missed by the device name addition, as the current release targets reliably have a device name if they are supported(as tested in CI), and newly added targets should conform to the spec. @0xc0170 @screamerbg @theotherjimmy: Open to solutions in the interim that won't confuse people.\r\n\r\nThe checks implemented in the changes #3172 should make it easier to warn a user about absent device names. That can come a follow-up PR. Not sure that will entirely solve the issue though."},"comment":{"url":"https://api.github.com/repos/ARMmbed/mbed-os/issues/comments/257839239","html_url":"https://github.com/ARMmbed/mbed-os/issues/3174#issuecomment-257839239","issue_url":"https://api.github.com/repos/ARMmbed/mbed-os/issues/3174","id":257839239,"user":{"login":"0xc0170","id":2963726,"avatar_url":"https://avatars.githubusercontent.com/u/2963726?v=3","gravatar_id":"","url":"https://api.github.com/users/0xc0170","html_url":"https://github.com/0xc0170","followers_url":"https://api.github.com/users/0xc0170/followers","following_url":"https://api.github.com/users/0xc0170/following{/other_user}","gists_url":"https://api.github.com/users/0xc0170/gists{/gist_id}","starred_url":"https://api.github.com/users/0xc0170/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/0xc0170/subscriptions","organizations_url":"https://api.github.com/users/0xc0170/orgs","repos_url":"https://api.github.com/users/0xc0170/repos","events_url":"https://api.github.com/users/0xc0170/events{/privacy}","received_events_url":"https://api.github.com/users/0xc0170/received_events","type":"User","site_admin":false},"created_at":"2016-11-02T11:28:51Z","updated_at":"2016-11-02T11:28:51Z","body":"@sarahmarshy Any proposals for this issue? I checked the referenced PR, and it contains just TargetNotSupportedException that says \"not in cmsis-packs\". What I see there, if IAR fails it could be because cmsis pack does not support it or IAR definition is missing  or IAR not supported toolchain, but can't locate the report message (to be clear what has not been found). Is this issue about it, how to make it more clear?\r\n\r\nShould a tool do a better error msg when it fails to export (what I saw in IAR exporter, 3 conditions that can fail):\r\n- ``iar toolchain is not supported for the target``\r\n- ``iar definition in iar_definitions.json is missing for the target``\r\n- ``cmsis-pack vXXX does not contain this target definition`` ?"}}
{"actor":{"display_login":"0xc0170"}}