Posts made by Maximilian Gerhardt

For each and every point you listed there is a mass of documentation available.

You should be able to install openssl on the Omega2+ (from LEDE repos or directly Omega repos), which gives you the means to generate what every certificate you like. You haven't mentioned what kind of certificate you need, with what cryptographic parameters (RSA/ECC, curves, modulo length, hash algorithm, ciphersuites and key exchanges to be supported,...). Actually you don't even have to install and use openssl on the Omega2+, you can generate the keys and certificates off-site.

Oh, I just had the orientation in the picture wrong. Looked at it upside down, my mistake.
The TX-,TX+ and RX-,RX+ are differential voltage signals for the ethernet PHY. They are NOT UART pins. See https://docs.onion.io/omega2-docs/expansion-dock.html for reference. UART1 pins are only RX1 and TX1.

@Mentor-Gashi If you are using a Arduino Uno or Arduino Nano, then that is a 5V device, too, so no level shifting was needed. The Arduino Pro Mini or the Omega2(+) are however 3.3V devices. If you wish to communicate between them, you need to supply the module with 5V and GND, plus a level shifter for TX and RX line (to convert Omega's 3.3V to 5V for the RFID reader, and to convert 5V from the RFID reader to 3.3V to the Omega, e.g. this).

Also, according to its wiki page (http://wiki.seeed.cc/125Khz_RFID_module-UART/), the module communicates with the UART settings 9600 baud (9600,No parity,8 data bit, 1 stop bit). For reading this input, I would either use screen or miniterm.py from the piserial python package (install via pip install piserial). For miniterm, you would e.g. use miniterm.py /dev/ttyS1 9600, then wait for some input. In your picture, you plugged the TX/RX lines into the wrong place. UART1 pins are on the left side of the expansion header (RX1, TX1). You also gave the RFID reader 3.3V and GND, not 5V and GND.

If you want a professional product you should be interested in using the PCB version of the Omega2+ on your custom-designed PCB, which is the Omega 2S or 2S+. From there, you can just connect the pins to connectors or whereever you need them. Price will depend on the number of PCBs ordered, plus internal design cost, et cetera. More infos on https://onion.io/omega2s/.

For low volume projects you could also design your own PCB in which a normal Omega2+ plugs into a female header socket. I presume the price of such a PCB, together with all the other components you need for that project, is lower than the price of the expansion board of 15$ (which basically contains a UART chip, a power regulator and female header socket).

The interesting bit is the requesting the ADC value: You have to read the datasheet very carefully, there is section 6 about reading data using a MCU. Your command byte 0xC0 is correct, but you have to send two 0x00 bytes to read the 10-bit response.

Actually, 0xC0 would be transmitted correctly in all cases. In my tests, byte values from 0x40 to inclusive 0xbf are wrong, and 0xC0 is just one above that. I'll get an Arduino, my Omega2 and a MCP3008 today, will attempt to read out the channel 0 with both devices, and compare SPI transfers with my logic anyalzer. After that, I will be able to tell you if the software is wrong or if the SPI failed. There are many factors involved, like hardware and sofware alike software (e.g. SPI configuration (speed, bit length of transfers, SPI mode 0 to 3,...)).

We are keep getting the emails with regards to SPI issue resolution. We are currently working on a new SPI driver that will hopefully fix or at least improve this situation.We are also testing it and hope to release it in Q3 or Q4 or this year. >However, we cannot promise the full resolution of this problem. Above all, it is possible to setup software based SPI. It would, at least, have an upper limit in speed. Thank you for reading, stay tuned.

If only it was at a more visible place, like a thread from the Omega Team with a list of things being currently worked on on their progress.. Well, but here we have it, maybe in Q4 (of which 2/3 are already over), we will have a fix. Or not, like with the deadline for a new WiFi driver. I'll keep this thread updated.

I am not very pleased to see that the original text I quoted on that helpdesk was now changed to

There isn't even any release date on there anymore. It's just "lol, we didn't get it working, but you can set up bit-banged SPI...".

I don't know anything about the LEDE build system, but I did build an emulator which was using libalsa. I managed to cross-compile it and link my programs against it. You can download the lib libasound.so and headers from https://github.com/gamer-cndg/omega2-libs. This worked for me where I was cross-compiling for my Omega2. Of couse, you'll have to install libalsa on your Omega2 for this to work, too. (opkg update && opkg install alsa-utils alsa-lib)