Skip to content

Conversation

@pkendall64
Copy link
Collaborator

This one just cleans up a lot of the defines that were there to disable certain features that were not available to STM32 based receivers.

@pkendall64 pkendall64 added V4.0 🍔 house keeping 🧹 Cleanup of code and house keeping labels Nov 11, 2024
Copy link
Member

@JyeSmith JyeSmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test with Nomad to BAYCK rx and mavlink... didnt break!

@Mkorho
Copy link

Mkorho commented Nov 11, 2024

Will external i2c baro still work with ESP8285 devices?
As there is lot of new defined(PLATFORM_ESP32) exclusions.
Or does ESP8285 belong to PLATFORM_ESP32?

I have many gliders that use ESP8285 based PWM receivers and i2c baro sensors.

@pkendall64
Copy link
Collaborator Author

Will external i2c baro still work with ESP8285 devices?

No, ESP8285 does not support the Baro sensors.

@Mkorho
Copy link

Mkorho commented Nov 12, 2024

No, ESP8285 does not support the Baro sensors.

So you are going to remove support in 4.0?

Quote from #2480

ESP8266 unified targets also can use barometers now as well

@pkendall64
Copy link
Collaborator Author

No, ESP8285 does not support the Baro sensors.

So you are going to remove support in 4.0?

Quote from #2480

ESP8266 unified targets also can use barometers now as well

Well then it should still work. I'll have to check when I'm back with my gear.

@Mkorho
Copy link

Mkorho commented Nov 12, 2024

And will USE_MSP_WIFI change to PLATFORM_ESP32 break TCP Betaflight configurator from all ESP8285 receivers?
#1274

@pkendall64
Copy link
Collaborator Author

And will USE_MSP_WIFI change to PLATFORM_ESP32 break TCP Betaflight configurator from all ESP8285 receivers? #1274

No, because that will just change to TARGET_RX

@Mkorho
Copy link

Mkorho commented Nov 12, 2024

And will USE_MSP_WIFI change to PLATFORM_ESP32 break TCP Betaflight configurator from all ESP8285 receivers? #1274

No, because that will just change to TARGET_RX

image
I am talking about this change.
And it is not TARGET_RX.

@pkendall64
Copy link
Collaborator Author

pkendall64 commented Nov 12, 2024

Oops, that is fixed in this PR now.

@pkendall64 pkendall64 force-pushed the phase-5-rx-device-cleanup branch from 118579d to e1a8c2d Compare November 12, 2024 03:55
@pkendall64 pkendall64 merged commit ef32864 into ExpressLRS:master Nov 12, 2024
@pkendall64 pkendall64 deleted the phase-5-rx-device-cleanup branch November 12, 2024 06:07
@mha1 mha1 mentioned this pull request Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

house keeping 🧹 Cleanup of code and house keeping V4.0 🍔

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants