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

Drop.inc Carina RGB Matrix port #11277

Closed
iakobou opened this issue Dec 22, 2020 · 5 comments
Closed

Drop.inc Carina RGB Matrix port #11277

iakobou opened this issue Dec 22, 2020 · 5 comments
Labels
help wanted question stale Issues or pull requests that have become inactive without resolution.

Comments

@iakobou
Copy link

iakobou commented Dec 22, 2020

This project aims to bring full QMK RGB Matrix support to the Drop.inc Carina 60% keyboard.

First and foremost, thank you to drashna, tzarc, and fauxpaux on either /r/olkb/ or Discord for many points of guidance in getting this project as far as it is.

I have forked QMK to host my project thus far: https://github.com/iakobou/qmk_firmware/tree/iakobou-carina-patch3.

I am happy to report that the firmware does compile successfully.

However, upon flashing it results in the Carina becoming inoperable with a flashing orange status light. I am afraid that it is beyond my capabilities now. I thought I'd put the link to the project here and maybe someone with better knowledge and know-how might want to pick it up in the future.

@vmalloc
Copy link

vmalloc commented Jan 5, 2021

I'm not 100% sure, but would it make more sense to port over the changes made in the official fork here: https://github.com/Massdrop/qmk_firmware/ ?

@iakobou
Copy link
Author

iakobou commented Jan 5, 2021

I used the official branch to make the carina directory in /keyboards/massdrop and then utilized the Massdrop fork to modify the carina.h, etc.

It compiles but it does not run successfully.

@drashna
Copy link
Member

drashna commented Mar 2, 2021

See #11119

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

@stale stale bot added the stale Issues or pull requests that have become inactive without resolution. label Jun 2, 2021
@stale
Copy link

stale bot commented Jul 8, 2021

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know.

@stale stale bot closed this as completed Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted question stale Issues or pull requests that have become inactive without resolution.
Projects
None yet
Development

No branches or pull requests

3 participants