silseva

Uh, no. It seems that the server from where you downloaded the nightlies is stuck. I downloaded and flashed an MD380 image from [our nightly server](https://files.openrtx.org/nightly/) and the version is...

No need to apologize! Do you remember from where you downloaded the "broken" nightlies? I'll keep this issue open for the late entry problem and close #144 as solved.

Yes, provided that you inject the signal externally, as the output stream driver is not implemented yet. The AT1846S driver already supports the transmission of digital modes.

The discussion here provides some hits, as the symptoms are similar: https://www.opengd77.com/viewtopic.php?t=2667 The MCUs installed in the new RT3s may be APM32F405: https://global.geehy.com/apm32?id=49

Test firmware to try tackle point 3: hw version field of info page contains the DBGMCU_IDCODE, interrupt level of audio stream drivers raised from 10 to 7. [openrtx_mduv3x0_test.zip](https://github.com/OpenRTX/OpenRTX/files/12841594/openrtx_mduv3x0_test.zip)

This is very interesting. Just to have another test, can you flash the latest nightly build with both the OEM firmware update tool and `radio_tool`, please? We'll also organize to...

After some investigations with Morgan ON4MOD we found out that there is something weird going on when writing to the MCU flash memory - were we're storing the settings and...

Hi, here https://github.com/silseva/MD380-boot-tests there are also some boot tests we used during the very first development phase to check if everything worked correctly. You have to wrap the executable's binary...

Super! Now you are trying to run also tests 3 and 4, I imagine. :) Did you managed to find the schematic of the radio, for working on it? PS:...

Hmm... the pins should be the same, since the MCU is the same and there are no alternate functions for the USB ones. Looking back in our notes, I found...