Configuring GPIO on LSC Battletron LED Bar with BK7231N After Flashing OpenBK

Question

Hello,

I bought this LSC Battletron LED bar at Action for 13€, it has a BK7231N (https://www.action.com/fr-fr/p/3202651/barre-led-de-gaming-battletron-razer-chroma/)
I successfully flashed OpenBK on it but I can't figure out how to configure the GPIO, I tried some pins but it didn't work.
I attach some images of the inside and a backup of the original firmware.

Thank you.

p.kaczmarek2 · Answer

I have extracted data from flash and it may shed some light:

Log in, to see the code

Text interpretation:


Device configuration, as extracted from Tuya: 
- Microphone (TODO) on P23
- IR Receiver is on P26
- SPI MISOmiso
- SPI MOSImosi
- Control Pin (TODO) on P6
Device seems to be using CBU module, which is using BK7231N.
And the Tuya section starts, as usual, at 2023424

This means this it has some addressable LEDs, we have a WIP driver for that, but it's not finished. Would you like to try it out? It may not work correctly for your kind of LEDs. Are those ws2812b?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

figurant17 · Answer

Yes, I can try.How to verify the model of the LEDs?

figurant17 · Answer

I tried the commands listed here: LEDs lit up once, but after a reboot, I couldn't get it to work again. Now I'm getting the following error with the last command SM16703P_Start: Error: CMD: before enable tx 0x0000c20cError: CMD: enable tx 0x0000c20dNot every LED turned on, 4-5 were missing.Thanks

eliovital9 · Answer

@p.kaczmarek2
I have the same problem with this item https://www.action.com/fr-fr/p/3202821/bande-led-gamin-rgb-battletron/.
The LEDs do not light up at all.


Error:CMD:before enable tx 0x00003e0c
Error:CMD:enable tx 0x00003e0d

I get the error when executing the command. Do you want more information to help debug the problem?

All commands logs:


Info:CMD:[WebApp Cmd 'startDriver SM16703P' Result] OK
Info:CMD:Register driver with 5 LEDs
Info:CMD:[WebApp Cmd 'SM16703P_Init 5' Result] OK
Info:CMD:Set Pixel 1 to R 255 G 0 B 0
Info:CMD:Raw Data 0xee 0xee 0xee 0xee - 0x88 0x88 0x88 0x88 - 0x88 0x88 0x88 0x88
Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 1 255 0 0' Result] OK
Info:CMD:Set Pixel 2 to R 0 G 255 B 0
Info:CMD:Raw Data 0x88 0x88 0x88 0x88 - 0xee 0xee 0xee 0xee - 0x88 0x88 0x88 0x88
Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 2 0 255 0' Result] OK
Info:CMD:Set Pixel 3 to R 0 G 0 B 255
Info:CMD:Raw Data 0x88 0x88 0x88 0x88 - 0x88 0x88 0x88 0x88 - 0xee 0xee 0xee 0xee
Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 3 0 0 255' Result] OK
Info:CMD:Set Pixel 4 to R 255 G 255 B 255
Info:CMD:Raw Data 0xee 0xee 0xee 0xee - 0xee 0xee 0xee 0xee - 0xee 0xee 0xee 0xee
Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 4 255 255 255' Result] OK
Info:CMD:Set Pixel 5 to R 100 G 100 B 100
Info:CMD:Raw Data 0x5a 0x5a 0x5a 0x5a - 0x5a 0x5a 0x5a 0x5a - 0x5a 0x5a 0x5a 0x5a
Info:CMD:[WebApp Cmd 'SM16703P_SetPixel 5 100 100 100' Result] OK
Error:CMD:before enable tx 0x00003e0c
Error:CMD:enable tx 0x00003e0d
Info:CMD:[WebApp Cmd 'SM16703P_Start' Result] OK

p.kaczmarek2 · Answer

It seems that your LEDs may be ws2812b. We would need to adjust our driver for that, ws2812b timings are a bit different than SM16703's.

I am not sure right now if ws2812b are marked in any way, but one could always try to temporary run the LED strip with ESP or Arduino to check.

eliovital9 · Answer

I confirm that it works well with the WS2812B chipset. I cut a section of my LED strip that I managed to control via ESPHome.

figurant17 · Answer

I tried too with an ESP and WLED and it's working well.

p.kaczmarek2 · Answer

Ok, good news, so I just need to get WS2812B running on OBK

snakesrules94 · Answer

Hi there,I've put a post in the temporary forum about this same game bar, with the same result...Now I've found this topic and realized that WS2812 are not yet supported by obk.@p.kaczmarek2: you can always have a look at the dump in my post as it seems different from the one in this post, maybe some glitch while dumping.Rgds.