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

Check MCU type at start #3272

Merged
merged 5 commits into from
Mar 13, 2023
Merged

Check MCU type at start #3272

merged 5 commits into from
Mar 13, 2023

Conversation

3djc
Copy link
Collaborator

@3djc 3djc commented Feb 27, 2023

Given the increased pressure on MCU sourcing, it becomes more likely that similar, or very similar radio get available with different MCU. This is already the case with TX12 and TX12-MK2, it will become more with upcoming T-Lite with F4 MCU.

On F2 hardware, F4 firmware do not start, but on F4 hardware, an F2 firmware starts and can appears to be running, when all timers and such are completely off, which can create great confusion.

This prevent running the firmware on MCU they where not compiled for. It includes all currently used MCU, as you never know whats comming

@voltangle
Copy link

I would've made the text "Bad MCU" instead of "WRONG MCU" imo

@pfeerick
Copy link
Member

pfeerick commented Feb 28, 2023

But bad can also be interpreted as "faulty"... so we'll then get support requests of "I updated EdgeTX and now it says my MCU is faulty... did I break it?" Even though this is specifically aimed at the wrong MCU for the target... it could be argued that "Wrong Firmware" (hm... would "Wrong FW" be enough?) is a bit more on the nose.

@voltangle
Copy link

Good point! But at least I would've liked it without CAPS, so that instead of "WRONG MCU" it's "Wrong MCU"

@pfeerick
Copy link
Member

Don't you start... the translators are going to be after me soon enough as it is insisting that it needs to be translated! 🤪

@3djc
Copy link
Collaborator Author

3djc commented Feb 28, 2023

I have choosen those terms to allow easier searching for solution, since occurence should be quite rare (also why I haven't made it translatable). Edgetx wrong firmware probably leads to too much answers, edgetx wrong mcu far far less.

@pfeerick
Copy link
Member

Exactly. And if we have a FAQ entry for that up pretty much straight away... there is a good chance it will come up as pretty much the first result if anyone searches for it...

@pfeerick pfeerick self-assigned this Mar 13, 2023
@pfeerick pfeerick added this to the 2.9 milestone Mar 13, 2023
@pfeerick pfeerick added the enhancement ✨ New feature or request label Mar 13, 2023
@pfeerick pfeerick merged commit 16a7f04 into main Mar 13, 2023
@pfeerick pfeerick deleted the 3djc/check-MCU branch March 13, 2023 06:13
philmoz pushed a commit to philmoz/edgetx that referenced this pull request Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants