[BUG] BTT Mini 12864 V1 incorrect colors on some STM32F4 & STM32H7 boards

[Lordcheche]

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

When selecting a preset color from the Lights menu the displayed colors are wrong. The config file is NEO_RGB, but for it to work properly it should be NEO_BRG. When selecting a custom color also from the menu it is bugged too. I know its the menu's fault because the when turning on my printer the default color is displayed correctly and all M150 commands work properly.

Bug Timeline

Since I started using Marlin

Expected behavior

When the color red is selected the screen turns red, with blue it becomes blue and the same with green.

Actual behavior

I select the red preset and the screen displays is blue

Steps to Reproduce

1. Turn on the printer.
2. Go to change the color thru the display of the printer.
3. It doesn't work.

Version of Marlin Firmware

2.1.2.1

Printer model

Custom printer.

Electronics

MOBO: BTT Octopus 1.1, Display: BTT Mini 12864 V1

Add-ons

No response

Bed Leveling

UBL Bilinear mesh

Your Slicer

Other (explain below)

Host Software

OctoPrint

Don't forget to include

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

Config.zip

[thisiskeithb]

This is an issue with some STM32H7 boards only and applies to all NeoPixels, not just the ones for this display. You can bypass the sanity check if your board is affected until a fix can be found.

[Lordcheche]

This is an issue with some STM32H7 boards only and applies to all NeoPixels, not just the ones for this display. You can bypass the sanity check if your board is affected until a fix can be found.

For my second strip every thing works fine. The problem is that even if i use another RGB config for example BRG (It fixes the presets), then the m150 commands won't work properly

[thisiskeithb]

The main issue is that this doesn’t affect all STM32H7 boards / configs the same way and there’s not an obvious reason why (like incorrect pins).

[Lordcheche]

The main issue is that this doesn’t affect all STM32H7 boards / configs the same way and there’s not an obvious reason why (like incorrect pins).

STM32F4 too? because i dont have a STM32H7 chip

[thisiskeithb]

STM32F4 too? because i dont have a STM32H7 chip

Apparently for some STM32F4 as well since NEO_RGB is correct for this display.