Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for the KW22D512 Kinetis MCU based USB Dongle #2943

Closed
zephyrbot opened this issue Dec 19, 2016 · 5 comments
Closed

Support for the KW22D512 Kinetis MCU based USB Dongle #2943

zephyrbot opened this issue Dec 19, 2016 · 5 comments
Assignees
Labels
area: Boards Enhancement Changes/Updates/Additions to existing features platform: NXP NXP priority: medium Medium impact/importance bug

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Dec 19, 2016

Reported by Johann Fischer:

Add support for the KW22D512 Kinetis MCU based USB Dongle for 802.15.4

  • USB-KW24D512, (manufacturer NXP, former Freescale)
  • phySTICK-KW2x, (manufacturer Phytec)

(Imported from Jira ZEP-1472)

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Hi Johann Fischer . This epic (which is currently planned for 1.7) is missing it's associated stories. You've been identified by Anas as the Assignee for this epic. Can you please associate the correct stories with this epic? We need to know which stories are to be done as part of this epic. Please add them in the "Issues in Epic" section above. If you need some help understanding how the Zephyr project uses epics vs. stories, please see this page: https://wiki.zephyrproject.org/view/Jira_Usage_Help. If you have any questions, please let me know. Thanks!

@zephyrbot
Copy link
Collaborator Author

zephyrbot commented Jan 9, 2017

by Johann Fischer:

Hi Mark Linkmeyer , I think epic is wrongly selected (my fault), the story would be enough and it would fit well to GH-2991.
Can I change it to Story?

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Hi Johann Fischer . Thanks for the quick reply. I went ahead and converted it for you and associated it with the other epic. Can you set the priority field? Use this for guidance: Highest = must-have in 1.7, High = should-have in 1.7, Med = nice-to-have in 1.7. Thanks!

@zephyrbot
Copy link
Collaborator Author

by Mark Linkmeyer:

Johann Fischer , in cleaning up issues in preparation of the move to GitHub issues, I cleared the FixVersion field for this story because it was set to 1.8 and 1.8 was already released. If you know when it is now planned to be released, please set the FixVersion field accordingly.

@zephyrbot zephyrbot added priority: medium Medium impact/importance bug area: Boards Enhancement Changes/Updates/Additions to existing features labels Sep 23, 2017
@jfischer-no
Copy link
Collaborator

done in 52923e6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Boards Enhancement Changes/Updates/Additions to existing features platform: NXP NXP priority: medium Medium impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants