05:15 <oneDragon[m]> I've recently been receiving messages directly from the CH304 TTL2USB module via UART.dr in the Raspberry Pi 4B

05:15 <oneDragon[m]> （I'm not sure if that's the right way to do, but after RTFM I have no ideas about what's the means of transmitter holding register.)

05:15 <oneDragon[m]> > if the FIFOs are not enabled, data is stored in the transmitter holding register (the bottom word of the transmit FIFO).

05:17 <oneDragon[m]> After i send this data from python script in PC to the serial in rpi4, It seems that only those with x below can be retrieved by getting UART.dr. I don't know how to do it right now, any advice?... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/OqaRZQWQUtjuwsZNElEWgaqr>)

05:17 <oneDragon[m]> * After i send this data from python script in PC to the UART in rpi4, It seems that only those with x below can be retrieved by getting UART.dr. I don't know how to do it right now, any advice?

05:17 <oneDragon[m]> 0x00, 0x0C, 0x81, 0x00, 0x00, 0x00, 0x00,

05:17 <oneDragon[m]> data = bytes([0xF1, 0x1F, 0xE2, 0x2E, 0xB6, 0x6B, 0xA8, 0x8A,

05:17 <oneDragon[m]> 0x02, 0x0F, 0x04, 0x01, 0x14, 0x14, 0x05, 0xBD]) # This is the binary data to send

05:22 <oneDragon[m]> * I've recently been receiving messages directly from the CH304 TTL2USB module via UART.dr in the Raspberry Pi 4B... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/XogDNKFcKwOYKODuXuTADkMT>)

05:59 <oneDragon[m]> Problem solved. Looks like the guy who wrote the driver forgot to turn on FIfO.

09:35 <pilipbeta[m]> Haha

12:15 <qzl[m]> I want to develop a TF card driver for SDIO protocol, where can I find the documentation for DesignWare MMC controller. I found that this documentation doesn't seem to be downloadable, is there any solution?

12:35 <marmrt[m]> SDIO is not an open protocol, you need to sign an NDA, or find the documentation through unoffical means

19:59 <MiloMoisson[m]> Can targets coexist in a workspace and if so, does someone has an example repository or could guide me ? I would like to unite 3 crates under a single workspace: `core` which targets `thumbv7m-none-eabi`, `controller` which targets current host, `transport` on which both crates depends, does build for both targets.

19:59 <MiloMoisson[m]> I could get them to coexist but ws-level `cargo build` won't work cause it tries to build platform specific `asm` to Intel `asm`. Also, if I want to run `core`, I need to pass `--target`. Though these issues wouldn't be a problem (I can just use a Just/Makefile instead). But my current setup with `probe-rs` doesn't correctly detect (I guess) which binary it should look the `defmt` table into and just refuses to log `RTT` data.

19:59 <dirbaio[m]> not possible, no

19:59 <dirbaio[m]> don't mix embedded and non-embedded code in a workspace

20:00 <netguru[m]> Yeah

20:01 <MiloMoisson[m]> How would you organize crates with different targets for the same project. It's kind of annoying to cd everywhere, no?

20:08 <dirbaio[m]> use cd, yes

20:08 <dirbaio[m]> * just use cd, yes

20:09 <dirbaio[m]> for rust-analyzer/vscode, just open one directory or the other

20:26 <JamesMunns[m]> <dirbaio[m]> "use cd, yes" <- Or two terminals!

21:23 <barafael[m]> workspace with different target crates is a hassle, don't