chore(hal): remove StdPeriph

[raphaelcoeffic]

Please note that the new GPIO driver has been ported from RIOT-OS.

[richardclli]

@raphaelcoeffic Please help to check what I have fixed, especially the sdram drivers.

[pfeerick]

Well, out of the seven transmitters I've tried so far, the Pocket, X9D+, TPro, T20 won't even boot up - just power led and maybe backlight, and only the EL18, PL18EV & TX16S are booting up with the current state of this PR... so something is majorly wrong atm. 🤪

edit: TX16S was just sat idling while I was typing this (as it often is as it's on a power supply), and it suddenly EM'd.

[3djc]

Well, out of the seven transmitters I've tried so far, the Pocket, X9D+, TPro, T20 won't even boot up - just power led and maybe backlight, and only the EL18, PL18EV & TX16S are booting up with the current state of this PR... so something is majorly wrong atm. 🤪

edit: TX16S was just sat idling while I was typing this (as it often is as it's on a power supply), and it suddenly EM'd.

Boot issues should be fixed.

But I think I found another one, jack trainer seem unavailable

[3djc]

Bootloader should be fixed.

T20 passthrough. Are we talking T20 or T20V2 ?

[pfeerick]

T20... Can try the V2.

…

On Sun, 26 May 2024, 4:47 pm 3djc, ***@***.***> wrote: Bootloader should be fixed. T20 passthrough. Are we talking T20 or T20V2 ? — Reply to this email directly, view it on GitHub <#5023 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJ66KPW2HCLWLNY4B3D2NTZEGARBAVCNFSM6AAAAABH2HXZGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA4TCNJUGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[3djc]

T20... Can try the V2.
…
On Sun, 26 May 2024, 4:47 pm 3djc, @.> wrote: Bootloader should be fixed. T20 passthrough. Are we talking T20 or T20V2 ? — Reply to this email directly, view it on GitHub <#5023 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ66KPW2HCLWLNY4B3D2NTZEGARBAVCNFSM6AAAAABH2HXZGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA4TCNJUGQ . You are receiving this because you commented.Message ID: @.>

Nop, seems to be all radio, on it

[pfeerick]

Yup, was just about to say Pocket also, thanks :)

[philmoz]

TX16S & EL18:

• Flashed via DFU, both firmware & bootloader work
• Flash bootloader from firmware SD manager - radio is bricked, neither firmware or BL will start. Requires DFU flash to recover.

T20V2 has the same issue.

[3djc]

Last remaining issues

• passthrough flashing
• possible crackling noise on boot (tx16s & t20v2, reported by Philmoz)

[3djc]

Afaik, no outstanding issues reported (yet ?)

[3djc]

Merge me merge me merge me :D

[pfeerick]

Last time you said that there was issues with bootloader, audio, major EM issues and ELRS passthrough (and more) so maybe not so vocal? 😆

…

On Sat, 1 June 2024, 12:26 am 3djc, ***@***.***> wrote: Merge me merge me merge me :D — Reply to this email directly, view it on GitHub <#5023 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJ66KJ2HOGHP67N4KFPOC3ZFCB7VAVCNFSM6AAAAABIS5LHSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSGM2TAMZQGU> . You are receiving this because you commented.Message ID: ***@***.***>

[gagarinlg]

But they have all been fixed
🙏

[pfeerick]

I hope so, but without actually testing the current state on several handsets again, I don't know? Do you? 😜 'cause bug fixes bugs *never* created any bugs themselves 🤣🤣🤣

…

On Sat, 1 June 2024, 5:42 am Malte Langermann, ***@***.***> wrote: But they have all been fixed 🙏 — Reply to this email directly, view it on GitHub <#5023 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJ66KIFRX3ZUY3VK57NIF3ZFDHB7AVCNFSM6AAAAABIS5LHSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSHA4DAMJYGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[pfeerick]

TPro:
🟢 boots, rf link (ELRS), telemetry, haptic, audio, usb joystick, usb SD, yaapu lua, elrs passthrough, able to flash bootloader from firmware, flash other firmware from PR bootloader
🟠 bootloader is still not quite right - is quite slow to start compared to pre PR, and is somewhat unresponsive to button presses when using. but is functioning. bootloader usb does not connect - attempts but does not enumerate.

TX16S:
🟢 boots, rf link (MPM Frsky X), telemetry, haptic, audio, flash internal MPM, usb joystick, usb storage, bootloader usb works, able to flash bootloader from firmware, flash other firmware from PR bootloader, random EMs appear to be gone

Pocket:
🟢 boots, rf link (ELRS), telemetry, haptic, audio, able to flash bootloader from firmware, flash other firmware from PR bootloader, usb storage, usb joystick, bootloader usb works

X9D+:
🟢 boots, rf link (XJT), telemetry, haptic, audio, able to flash bootloader from firmware, flash other firmware from PR bootloader
🟠 bootloader is still not quite right - is quite slow to start compared to pre PR, and is somewhat unresponsive to button presses when using. but is functioning. bootloader usb does not enumerate

T20:
🟢 boots, rf link (ELRS), telemetry, haptic, audio, bootloader usb works, usb storage, elrs passthrough, able to flash bootloader from firmware, flash other firmware from PR bootloader,

PL18EV:
🟢 boots, rf link (ext MPM, Frsky X), telemetry, haptic, audio, able to flash bootloader from firmware, usb storage, usb joystick, bootloader usb

EL18:
🟤 still having issues with SD card that came with one EL18, will need to investigate further to determine culprit, but it seems sd card specific

Considering the issues still outstanding (that we know of so far) can be mitigated by simply not updating the bootloader until they are resolved, I have no issue with merging this now and fixing up on the fly. Just to elaborate further on the sluggish bootloader / no usb enumeration, I also tried the TX12 in addition to the prior radios, and it had the issue also, so would appear to be common to STM32F205xE radios ;)

[richardclli]

I have played around my EL18 and did not spot any problems, so what is your SD card problem about?

[pfeerick]

See #5023 (comment)

Basically it would boot up, get past the warnings, and then reboot into a endless loop where it would vibrate and then reboot again.