-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test using the MAX14830 for serial multiplexing. #7
Comments
Am I correct in reading that this is an SPI/I2C to UART bridge? |
yeah, spi to 4 uart |
for a total of five uarts on the pi. |
Hi MAX14830 is an option. For the SPI interface there exists a module in the mainstream kernel http://elixir.free-electrons.com/linux/v4.12-rc7/source/drivers/tty/serial/max310x.c I have shared a version that works with the I2C interface: This requires working at the kernel level and device trees. You will have to compile the kernel. Another option, which does not require kernel level knowledge, is to use a USB to UART HUBs based on for example FTDI FT4232H http://www.ftdichip.com/Products/Modules/DevelopmentModules.htm#FT4232H_Mini This latter is around €27. The boards I have with 14830 were custom designed and required soldering in an SMD oven... will be more expensive for small batches. I did get an Evaluation Kit at first, over €100... |
Sadly there are no free USB ports IIRC. We had a USB hub in Kitty and used an FTDI, but it just took up loads of space, something Captain Morgan is pretty much designed to try and save |
Yeah part of the whole long term goal is to remove the need for USB devices and it's not out of the realm of possibility to solder a qfn by hand with the right footprint. I would be interested in knowing what sort of baudrate speeds you were able to get reliably with the i2c bus. |
ah! only now I noticed this is for a robotic sailboat. Marine engineer on this side. I was interested in getting 8 UART for an automation project, did so by using two 14830 on I2C. However, the board I used was the ARIAG25 and the module was the one I shared for kernel level. I did not test in RPi. I did not require high rate, 9600 bps is what I've been using on all ports at once. The device works in I2C but has buffer and interrupt driven reading. I think you could get away soldering with hot air. Do you use Eagle PCB design software? I have schematics of the working 8 port circuit and would reduce it to 4 and share if that could be of use. |
We use the KiCAD EDA package because it is open source, but I would love to see your schematic for reference, I hadn't considered using the i2c bus as I assumed that it would be too slow, but if you got it running at 9600 then it might be an interesting solution. |
Should be enough to evaluate if you want to go that way. |
I am using raspberry pi. can you post the device tree for MAX14830 over SPI. I am struggling to get the MAX14830 get work. |
Sorry but I haven't used SPI or RPi with the device. If you have an oscilloscope I would recommend that you try to put hardware problems aside, otherwise, if you have not tried I2C, I would recommend some common ground with respect to what I have. This means I2C, which should be relatively simple in this case because SPI and I2C pins are shared on the device. Enable I2C on the RPi. Then with everything connected I would use shell command $i2cdetect -y dev dev depends on which I2C bus you are using (0 or 1). Only once hardware problems are set aside and the device is detected (try also without device to make sure it is the device that is responding) then you could try the driver I modified and the part of device tree which respects to the device. For I2C device at 6C
|
@sbharsha me too! |
Can I ask if @Droid-MAX or @sbharsha managed to get the MAX14830 working via SPI, I would really appreciate any assistance on this one. |
I would like like to try using the MAX14830 to add some extra UART ports to the Pi, there should be a linux driver.
The text was updated successfully, but these errors were encountered: