@crispyoz is what you have running under test an Onion firmware version running with OpenWrt 22? We have a dependency on Python 3.9 and we would like to also use the stm32flash library that was introduced in OpenWrt 21. Would your version be available to trail, maybe from a branch?

Thank you @JeffZhou and @crispyoz the schematic is good.

It turns out the symbol/footprint we used in the design was incorrect. With a micro SD adapter soldered to the pins a range of cards were successfully detected and mounted.

The carrier quality is good so for anyone wanting to use it, these links helped:

There is stock available here.

Digikey has some good document references for the carrier here.

SnapEDA has a great symbol and footprint for the carrier here.

Hi,

I have a custom board with an Omega2S+ which uses this SD Card Connector. The data sheet is here.

The card is NOT mounted automatically and the following messages are appearing in the kernel log:

Below is our schematic for the connector, it was derived from the reference schematic here:

Is there anything obvious that I have missed here?

Any help would be much appreciated.

Thanks,

Tim

@crispyoz yes dropping the baud rate does enable the pro board to communicate with the serial device.

Using an arduino nano at 3.3v connected to the same serial device the two can communicate at 115200 reliably.

Seems to be an issue with the Omega2s+ at 115200

@crispyoz thank you for you help.

Using minicom yields the same result.

minicom -D /dev/ttyS1 -b 115200

I connected a 3.3vdc Ardunio nano to the same serial interface at 115200 and it is reading the correct data response.

Using an Omega2 Pro I'm communicating with a serial device on /dev/ttyS1 baud 115200 81N - the inbound payload from the device is corrupted:

Command

screen /dev/ttyS1 115200

yields:

Using a logic analyzer I can see on RX1 PIN 46 that the data is correct:

The outbound command to the device is correct and the device responds with the expected message.

Any help would be greatly appreciated.