Allow debug console to be used for other protocols

[tridge]

This allows the debug console on FMUv2 and FMUv3 to be used for other serial protocols, by setting SERIAL5_PROTOCOL to an appropriate value.
fixes issue #6692

[proficnc]

Thankyou Tridge!

[robustini]

Thanks you Andrew! Number One!

[jmachuca77]

Awesome! Best regards, Jaime Machuca CEO | Element Aero | www.element.aero Mail. jaime@element.aero Off. +52 (33) 3805 4627 Cel. +52 1 (33) 3945 3350 Este correo electrónico y cualquier archivo transmitido en él, son confidenciales y para uso exclusivo de los individuos y entidades a quienes está dirigido. Si usted no es el destinatario previsto o la persona encargada de recibirlo, y tiene por error este mensaje, queda prohibido y sin validez el uso, difusión, re-envío, reimpresión o copia. Toda oferta y/o aceptación de propuestas comerciales, celebración de contratos u otros actos tendientes a la adquisición de bienes o servicios, así como el establecimiento de cualquier clase de obligación legal para Element Aero SAPI de CV, deberá confirmarse por escrito firmado autógrafamente por funcionario competente, excepto que se cuente con un contrato vigente que autorice el uso de este medio para tales fines. Si usted recibió este correo por equivocación, favor de notificar inmediatamente por este medio a su remitente, y después borrarlo de su correo

…

On Aug 13, 2017, at 8:49 AM, Marco Robustini ***@***.***> wrote: Thanks you Andrew! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[WickedShell]

@tridge If I'm following right the port still starts up as NSH first with some prints from the PX4 layer, then once the APM task is launched it's killed?

[proficnc]

We should ensure the comments that come with the parameter on the ground stations reflect this.

And we should engage the community to ensure this has no effect on various devices.

That way we can just swap devices to a suitable port.

This is very good!

[tridge]

@tridge If I'm following right the port still starts up as NSH first with some prints from the PX4 layer, then once the APM task is launched it's killed?

that's right. The only way we could avoid that is to have some persistent data that can be read by the very early startup code that indicates that the nsh debug port is disabled.
Given that you are free to arrange your UARTs in any order you like I don't think this is a big issue. Many (most?) devices won't care if they get some debug stuff at startup, so just choose one for SERIAL5 that doesn't care, such as a telemetry radio.

[OXINARF]

LGTM. It could also be implemented for Pixracer, but that has 5 ports already, should be enough for most use cases.

[robustini]

Please merge this commits...

[tridge]

merged

[PlanetKrikkit]

Forgive my ignorance, but I would like to user serial 5 to stream Mavlink to an Alexmos gimbal controller. The gimbal controller manual recommends some message stream rate values, but although I can set serial5_protocol to be '1' i see no sr5_xxx parameters (or sr4_ for that matter) to allow me to configure the messages/rates required. Am I missing something?