beaglebone black RS232 cape troubleshooting

I'm running a default build of Angstrom on a BBB with a CircuitCo RS232 cape, and I can't get the cape to communicate via the RS232 cape with a Juniper router, which needs 9600n1 settings. I eventually want to connect it to a Morningstar solar controller using serial/modbus, but it's on a very cold mountaintop, so I need to verify it will work first using 9600n1. I am able to use minicom on my laptop and get a login prompt to the router using those settings, so I know my cables and set up are right, but not on the BBB. I am using UART2, which is enabled in uboot/[url removed, login to view] using the console directive (In addition to the default ttyO1. When I duplicate that console directive and just change the console to ttyO2, it hangs on boot. I have tried flashing the eMMC to Debian Wheezy (using Robert Nelson's image and also an armhf one from somewhere else, and neither of them allow me to successfully pass the appropriate bootargs to make my console recognize the cape, either with jumpers on UART1 or 2 (but the install/config was successful), so now I'm trying to revert to Angstrom for troubleshooting purposes. When using Angstrom OS, I have the right entry in my slots, and dmesg *seems* to see the cape, but it still won't communicate. I've RMA'ed the cape and now have a new one. I have ordered a replacement BBB, in case that helps as a troubleshooting step (though they are backordered for awhile on DigiKey, so who knows when it will get here). I'm also open to other platforms to accomplish the same thing, but it's critical it uses as little power as possible - I can't use over 2W, and I *think* the Raspberry Pi uses around 5 (from what I've read). OTOH, if there's a better serial server which will allow me to assign an IP address to the converter and address the modbus over RS232, that would be fine. But a BBB would have a lot more flexibility as a server, not just a serial server.

Linux

Projektazonosító: #5249966

A projektről