Yield-based vs multi-core approach to async TX

[phretor]

Is your feature request related to a problem? Please describe. No, pure enhancement.

Describe the solution you'd like The transmit blocks the core until TX is fully completed. Is this based on the assumption that the WiFi (for instance) and other tasks will run independently on CPU0? Have you considered reading the radio state before starting a transmission and don't block but use IRQs to mark a successfull TX?

Describe alternatives you've considered Using ESP8266 and some of Arduino's yield.

Example: Example: https://github.com/trendmicro/RadioHAL/blob/master/src/RH_CC1120.cpp#L274

What do you think? My apologies if there is a discussion board/ML/chat to discuss this prior to open an issue: I haven't found any. In that case, please point me there and just close this issue.

[jgromes]

transmit methods are indeed blocking, but they are just a "wrapper" on top of few non-blocking methods. All radio modules follow the basic approach that transmit = startTransmit + blocking while loop. You can just as well use startTransmit to start the transmission and then handle the waiting or interrupts yourself.

RadioLib was originally written for Arduino Uno, hence no multicore support or considerations.

There's no discussion board, I think GitHub issues are the best place to discuss bugs/new features for a library of this size.

[phretor]

I’m wondering what will happen if the user calls startTransmit fast enough, such that the previous transmission hasn’t finished. Will everything just crash, or the TX FIFO will be overwritten before the previous transmission is finished, or nobody except the chip manufacturer know?

I’ve never tried, so I’m just thinking aloud :-)

On 11 November 2019 at 16:07:52, Jan Gromeš (notifications@github.com) wrote:

transmit methods are indeed blocking, but they are just a "wrapper" on top of few non-blocking methods. All radio modules follow the basic approach that transmit = startTransmit + blocking while loop. You can just as well use startTransmit to start the transmission and then handle the waiting or interrupts yourself.

RadioLib was originally written for Arduino Uno, hence no multicore support or considerations.

There's no discussion board, I think GitHub issues are the best place to discuss bugs/new features for a library of this size.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jgromes/RadioLib/issues/60?email_source=notifications&email_token=AABPCNDQJRZ2RPZIVQVPYBDQTFYMRA5CNFSM4JLWTGMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDXDMMY#issuecomment-552482355, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABPCNAXVTRVADSHOA4A2OTQTFYMRANCNFSM4JLWTGMA .

[jgromes]

I'd assume current transmission will be stopped since standby mode is set prior to tx start. and the FIFO will be overwritten - never tried it though and I don't suggest you do ;)

One possible exception from the above could be SX126x becuase of the BUSY pin, but again - never tried this.