-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
SpeedyBeeF7 No led strip #7234
Comments
I don't own this board but I think you also need to define the CPU pin number that is hooked to the LED pad. The target.c file lists the LED timer to be on the PB7 pin (if this is correct it should be connected to the LED pad) inav/src/main/target/SPEEDYBEEF7/target.c Line 35 in 7f1b2cd
So you need to add these lines to the target.h file after line 143 (just above the "FC Default Config" section) I've tested the code and it will build but I have no hardware to test? Hope this helps - Rich |
Thanks Rich, will test this out |
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. |
Hi, Actual target.c (src/main/target/SPEEDYBEEF7V2/target.c ) define PB0 as led pad So the correct defintion of target.h should be PB7->PB0 // LEDSTRIP I tested with an 8 led stripe and seems working correctly. |
There are three different SPEEDYBEEF7 targets. If your working with the original target board then PB7 is the pin listed in that target.c file Rich |
That's right.
I tested the V2 version.
|
Looks like it works on your target V2 with PB0 as I see you linked a PR for the change. It should also work on the original target with PB7 but never got a test response from @charizardavi |
I will test it soon, thank you so much for all the support. |
The Speedybee f7 does not have led strip support currently, is there any way to add it? I tried adding "#define USE_LED_STRIP" in target.h, got a build error relating to the led strips.
The text was updated successfully, but these errors were encountered: