{"action":"created","issue":{"url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware/issues/156","repository_url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware","labels_url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware/issues/156/labels{/name}","comments_url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware/issues/156/comments","events_url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware/issues/156/events","html_url":"https://github.com/UltimateHackingKeyboard/firmware/issues/156","id":351662709,"node_id":"MDU6SXNzdWUzNTE2NjI3MDk=","number":156,"title":"Dev docs refinements","user":{"login":"kareltucek","id":3447497,"node_id":"MDQ6VXNlcjM0NDc0OTc=","avatar_url":"https://avatars2.githubusercontent.com/u/3447497?v=4","gravatar_id":"","url":"https://api.github.com/users/kareltucek","html_url":"https://github.com/kareltucek","followers_url":"https://api.github.com/users/kareltucek/followers","following_url":"https://api.github.com/users/kareltucek/following{/other_user}","gists_url":"https://api.github.com/users/kareltucek/gists{/gist_id}","starred_url":"https://api.github.com/users/kareltucek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kareltucek/subscriptions","organizations_url":"https://api.github.com/users/kareltucek/orgs","repos_url":"https://api.github.com/users/kareltucek/repos","events_url":"https://api.github.com/users/kareltucek/events{/privacy}","received_events_url":"https://api.github.com/users/kareltucek/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-08-17T16:40:51Z","updated_at":"2018-08-24T07:51:30Z","closed_at":"2018-08-21T14:12:56Z","author_association":"NONE","body":"I've read through the docs of the three main repositories (agent, firmware, bootloader). Yet, I find some points unclear (with respect to minimum configuration needed for firmware tweaking of a factory set-up UHK):\r\n\r\n- I assume that flashing (locally built) bootloader onto UHK with factory bootloader is not necessary, right? \r\n\r\n- Furthermore, I assume that the J-link probe is not necessary for higher-level firmware hacking?\r\n\r\n- When I open uhk-right project, MCUxpressoIDE shows error `Unable to find part support for NXP MK22FN512xxx12 in project uhk-right Resetting to generic part for core null\tuhk-right\t\tUnknown\tProblem`. However, it can build the project fine.\r\n\r\n- If I ignore the bootloader and j-link probe, the dialog in the step `Then in KDS, click on Run -> Run Configurations, select C/C++ Application -> uhk60-right_release_kboot, and click on the Run button.` shows error `Program not specified`, apparently requiring specification of the 'C/C++ Application' field (which is empty). \r\n\r\n\r\n\r\n "},"comment":{"url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware/issues/comments/415681674","html_url":"https://github.com/UltimateHackingKeyboard/firmware/issues/156#issuecomment-415681674","issue_url":"https://api.github.com/repos/UltimateHackingKeyboard/firmware/issues/156","id":415681674,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNTY4MTY3NA==","user":{"login":"kareltucek","id":3447497,"node_id":"MDQ6VXNlcjM0NDc0OTc=","avatar_url":"https://avatars2.githubusercontent.com/u/3447497?v=4","gravatar_id":"","url":"https://api.github.com/users/kareltucek","html_url":"https://github.com/kareltucek","followers_url":"https://api.github.com/users/kareltucek/followers","following_url":"https://api.github.com/users/kareltucek/following{/other_user}","gists_url":"https://api.github.com/users/kareltucek/gists{/gist_id}","starred_url":"https://api.github.com/users/kareltucek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kareltucek/subscriptions","organizations_url":"https://api.github.com/users/kareltucek/orgs","repos_url":"https://api.github.com/users/kareltucek/repos","events_url":"https://api.github.com/users/kareltucek/events{/privacy}","received_events_url":"https://api.github.com/users/kareltucek/received_events","type":"User","site_admin":false},"created_at":"2018-08-24T07:51:30Z","updated_at":"2018-08-24T07:51:30Z","author_association":"NONE","body":"> I've just updated them. \r\n\r\nThanks very much! Instructions now see clear to me and I can flash from IDE.\r\n\r\n> Not sure about the \"Unable to find part support...\"\r\n\r\nSince everything seems to work, I would probably leave it be (unless you are interested in the output?). \r\n\r\n> What do you want to tweak in the firmware exactly?\r\n\r\nNo exact plans yet. So far, I've been doodling with layer switching code and macro player - just to find my way around the code of firmware and agent. \r\nThe following points are currently of interest for me:\r\n\r\n- Generalization of layer switching I.e., \r\n  - Refactoring switching so that the base layer is no longer special. This means allowing toggling layers from non-basic layers and activating one \"hold\" layer from any toggled layer.\r\n  - Maybe allowing nested activation of \"hold\" layers.\r\n  - (The idea is that agent's side would allow advanced mappings only with a special flag (like \"advanced features\" checkbox somewhere), altering firmware's behaviour only on those serialization cases which are currently not used at all by the agent.  )\r\n\r\n-  If #157 turns up to be a problem, then I might need to deal with it somehow. (So far, I don't mind the behaviour (as long as it is consistent) with respect to use-cases which I can foresee. However, I still fear that the logic might become problem under some circumstances.)\r\n\r\n- Adding some functionality to macro engine - I am missing layer/keymap switching. \r\n\r\n- Also, adding some generic support for adding arbitrary firmware-sided functionality via macro engine would be nice (i.e., coding agent so that adding new firmware-sided features is not so painful).\r\n\r\nShould I fire these as separate feature requests? \r\n\r\nMy current idea is to allow bindings that smooth out the workflow - i.e., to switch layers implicitly on actions. (A bit like vim's modes - the idea is to use only commands and let the editor (keyboard) switch layers according to their context.) \r\n\r\nBtw is this style of doc/dev questions/requests preferred or should I get in touch directly?\r\n\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"kareltucek"}}