Quick update: SUCCESS! I now have serial communication occurring through the Comms cape RS485 port. However, I need to reverse the lines: A must go to B and B must go to A between the two devices.
The correct way to hook up RS485 devices is to daisy-chain all the A's together and all the B's. I believe that the Comms cape is simply mislabeled. This may derive from a reversal in the schematic or something. The latest Debian Linux version is able to accomplish this enabling of the Comms cape RS485 port, as long as the uEnv.txt file enables UART4 in the standard manner. You can also use "config-pin" command to enable the pins, and it works. -Todd On Thursday, June 6, 2019 at 8:29:19 PM UTC-4, [email protected] wrote: > > We recently purchased the GHI Comms cape, in order to have a nice RS485 > port available. > However, even the latest Debian image for the BeagleBone black does not > have the required overlay dtbo file! > When the BeagleBone Black boots, I get this: > [ *1.493924] bone_capemgr bone_capemgr: loader: failed to load slot-2 > BBORG_COMMS:00A2 (prio 0)* > The cause is that the file BBORG_COMMMS-00A2.dtbo is missing. > And sure enough, there is no overlay written for this cape in: > > https://github.com/beagleboard/bb.org-overlays > > I am guessing that there is an alternative way to get this Cape up and > running. I’m moderately OK with linux as a user and admin, but rather new > to IoT. > > > Best, > Todd > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/93cf80cc-4ea3-4306-88ec-ba6e39c6d319%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
