This chip only has a single hardware uart, it seems. But I can probably get the HET emulated one running again.Is that thinking for the future or needed soon?73,Burns Fisher, WB1FJAMSAT(R) Engineering -- Flight SoftwareOn Mon, Dec 5, 2022 at 11:40 AM Chris Thompson <chrisethompson@gmail.com> wrote:Burns,Any chance that we can have a second debug UART? That would be very helpful. It would output KISS AX25 bytes and bypass the radios. We could connect it directly to the ground station (which also uses KISS to talk to its TNC). We could then debug all of the state machines for the PACSAT Protocol without needing to use the radios.We could also make it work with the existing UART in a special debug mode where printf is disabled perhaps. But that sounds like it would break things.73ChrisOn Mon, Dec 5, 2022 at 10:46 AM Burns Fisher (AMSAT) <wb1fj@fisher.cc> wrote:-----------------------------------------------Hi All,I've just merged in a branch (after testing by Chris) which has a HALCoGen configuration that is specifically for the LaunchPad. In addition, I've moved the console to be on a real UART rather than the N2HET emulated one (which has some problems with missing characters). The console serial connections are now:Ground: pin 32Rx: Pin 33Tx Pin 34Chris and I are both able to talk to the 5043 chip on the Pi board, but at some point during initialization, the crystal stops oscillating. As soon as I get a couple MRAMs to use (maybe today or tomrorow?) I'll try to get them set up both to sleep when not in use and to make the fact that there are multiple MRAMs transparent--just specify an address and it will choose the right one.73,Burns Fisher, WB1FJAMSAT(R) Engineering -- Flight Software
pacsat-dev mailing list -- pacsat-dev@amsat.org
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org
To unsubscribe send an email to pacsat-dev-leave@amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
--