**** BEGIN LOGGING AT Thu Dec 20 03:00:01 2018 Dec 20 03:43:58 zmatt don't gouge your eyes out just yet, you still have atrociously written drivers from random vendors too look forward too. Dec 20 03:45:14 that said TI does seem to have it's fair share of hacked together code. I swear it's all DEMO quality. Same thing with ST- there stuff stinks too only worse. Dec 20 05:45:14 Hi guys, Please tell me the configuration for the UART pin to Fullcross RS232 cable data transmission. Dec 20 05:51:08 I there any way to connect the full cross Serial port in BBB Dec 20 06:20:04 newbee: do NOT connect RS-232 directly to the BBB. You MUST use a level shifter. Dec 20 06:36:18 @tbr I use the Rs232 to TTL converter for connection. But Now I need to know how to connect the fullcross cable in BBB. Dec 20 06:37:09 I can connect the Basic cross cable and I tested in BBB. Can you please help me with this. Dec 20 06:37:35 what do you mean by "full cross" and which UART are you connecting to? Dec 20 06:40:02 so you want to hook up DTR/DSR, RTS/CTS too? Dec 20 06:42:04 @tbr Please see this cable configuration http://www.wifimove.com/RS232%20Full%20Cross Dec 20 06:43:14 OK, yes. Which of the 5 or 6 BBB UARTs do you want to connect this to? Dec 20 06:44:35 @tbr Any one in the UART group ttyS1,S2,S4,S5 Dec 20 06:47:41 you need all the modem control signals too? I think only uart1 has those Dec 20 06:48:13 which also means you'll need a lot of rs232 drivers Dec 20 06:49:38 oh actually, never mind, those pins are not accessible on the beaglebone (or already used for other purposes) Dec 20 06:49:53 not sure if linux supports using random gpios for modem control signals Dec 20 06:50:13 RTS/CTS is colliding with HDMI/LCD for UART 2,3,4,5 Dec 20 06:50:27 @zmatt in BBB there are only has RTS/CTS only. Dec 20 06:50:45 yeah rts/cts is available on other uarts, the remaining modem control signals aren't Dec 20 06:51:17 like tbr said, it does conflict with video, but you can disable that if you don't need it Dec 20 06:52:35 @zmatt OK, what about DTR/DSR Dec 20 06:53:37 like I said, only uart1 has those but the pins are not accessible on the beaglebone. maybe linux supports using random gpios for dtr/dsr but I'm not sure Dec 20 06:55:21 it's quite uncommon for anyone to actually care about those oldfashioned modem control signals Dec 20 06:55:40 @zmatt sorry for asking again which are the pins to enable DTR/DSR, can you please tell me the pin numbers.. Dec 20 06:55:52 THERE ARE NONE ACCESSIBLE Dec 20 06:56:28 @tbr Okay.. Dec 20 06:56:55 if you *really* require those, you can research if Linux allows you to use GPIOs for those Dec 20 06:58:16 @tbr thanks for the info.. Dec 20 07:00:57 for my clarification the BBB serial port pin out diagram only shows the CTS/RTS pinouts for UART1, But You told that UART1 has those but not accessible.. Dec 20 07:01:53 07:50 < zmatt> yeah rts/cts is available on other uarts, the remaining modem control signals aren't Dec 20 07:02:52 it helps to actually read what people say Dec 20 07:03:04 IF you disable HDMI Dec 20 07:03:15 uart1 rts/cts doesn't conflict with video Dec 20 07:03:19 yes, please read the needful Dec 20 07:03:42 uart2-5 rts/cts conflicts with video, hence would require disabling video Dec 20 07:04:14 uart1 rts/cts conflicts with the cape i2c bus though Dec 20 07:04:27 which is arguably even worse Dec 20 07:05:33 tell me if i am wrong, We can use RTS/CTS in ALL available UART's But need to sacrifice HTMI and video ou. But We can't use DTR/DSR in BBB right.. Dec 20 07:05:50 so if you want rts/cts, the option is to use uart 2, 4, or 5, and disable video Dec 20 07:06:00 *the best option Dec 20 07:06:49 dsr/dtr would have to use gpios, which is theoretically no problem but I don't know whether the linux driver supports it currently Dec 20 07:09:40 @zmatt my current requirement is to use the **Full cross serial cable** to read/write in BBB. So that i need RTS/CTS and DTR/DSR. Dec 20 07:10:22 you have already said that Dec 20 07:10:41 note that the "full" cross cable also has DCD and RI Dec 20 07:10:43 I am clear with RTS/CTS but I cant find solution for DTR/DSR Dec 20 07:10:52 which probably can just use GPIOs too Dec 20 07:11:31 actually dcd/ri can't possibly be supported by a cross-cable Dec 20 07:11:47 since they'd be configured as inputs on both sides, hence would be useless Dec 20 07:12:04 seems there are some common wiring setups for that: https://en.wikipedia.org/wiki/Data_Carrier_Detect#As_used_with_null_modems Dec 20 07:12:32 or per hardware configuration defined direction Dec 20 07:13:28 yeah they connect dcd and dsr together (to the dtr of the other side) Dec 20 07:13:42 https://en.wikipedia.org/wiki/File:D9_Null_Modem_Wiring.png Dec 20 07:16:24 so we need to use the null modem.. Dec 20 07:16:52 ? Dec 20 07:17:32 Sorry I am asking you.. Dec 20 07:17:32 are you able to tell us what you are going to do with this? Dec 20 07:18:05 you said you needed to use a null modem cable (aka "cross" cable) Dec 20 07:20:07 @tbr we are communicating to the equipment that transfer the data through the full cross cable. Dec 20 07:21:04 are you able to tell us what sort of equipment that is? Dec 20 07:21:25 @tbr No I am not saying that I am going to use null modem.. Dec 20 07:21:49 what? Dec 20 07:22:50 @tbr like gps devices Dec 20 07:25:46 most GPS receivers are fine with RX/TX/GND. Dec 20 07:25:47 most devices require a normal cable, not a cross/null-modem cable. also, most devices don't require dsr/dtr Dec 20 07:25:55 even rts/cts is uncommon Dec 20 07:27:31 And also some medical equipements... Dec 20 07:30:07 Before trying to recreate a full TIA-232-F port. *I* would verify if that's even needed, because that's considerable software and hardware engineering effort Dec 20 07:34:22 @tbr some of the medical and gps equipments needed both RTS/CTS and DTR/DSR. Generally I use Serial to usb hub in linux. But in BBB it already has the Serial so I need to enable those in BBB alsoi.. Dec 20 07:35:16 Can you please tell me how to configure the GPIO pins for DTR/DSR pinouts Dec 20 07:43:47 I'd suggest to look at the kernel documentation for serial port drivers to see if you can just define DTR/DSR as GPIOs in DT Dec 20 07:47:05 @tbr please advice me which kernal documentation for BBB. I used debian OS. Dec 20 07:47:57 Debian version 9.5(IOT) streach Dec 20 07:48:22 http://bfy.tw/LREv Dec 20 07:50:06 Ok I will try this... Dec 20 07:55:30 this one is for free: "linux kernel documentation serial device tree bindings" Dec 20 08:06:17 @tbr Ok Dec 20 08:21:57 hi, is there a borad available with 2 network interfaces and consums less than 6 W? Dec 20 08:23:22 Hi Dec 20 08:23:58 Is threre a board with 2 network Interfaces? Dec 20 08:24:21 you mean in the Beagleboard family? Dec 20 08:24:29 yes. Dec 20 08:24:53 there's the X15, but that probably consumes more than you like and is pricy Dec 20 08:24:53 .. and with less than 6W power consumption. Dec 20 08:25:09 also there's the industrial EVM Dec 20 08:25:27 great! Dec 20 08:26:09 Do you have the figure of the Power Consumption? Dec 20 08:26:28 for what? Dec 20 08:26:47 for the X15 board. Dec 20 08:29:04 the PSU recommendation is minimum 60W at 5A. Actual power consumption is probably much less Dec 20 08:29:17 JS__: there's also the phytec wega Dec 20 08:29:47 also the TMDSICE3359 is the earlier mentioned industrial eval board Dec 20 08:29:50 JS__: basically thats a beaglebone black with two nics Dec 20 08:32:39 neat, more reasonable price, though limited to 10/100M. the ICE can do 1000M link up (and throughput was IIRC 200-300MBit tots?) Dec 20 08:33:15 sure. its an option, depending on your price/performance/availability demands. Dec 20 08:33:23 Many thanks. I will look into the TMDSICE3359 board and the ICE bard. Dec 20 08:40:47 The ICE2 board is very interesting. Dec 20 13:27:49 tbr: the x15 psu requirements is in no small part for the usb3 and esata ports Dec 20 13:30:19 zmatt: exactly, though I remember the thing also getting quite warm or was it that it at least had a fan or such Dec 20 13:30:29 mine has no heatsink or fan Dec 20 13:30:37 oh, ok Dec 20 13:30:49 pretty sure mine does. haven't touched it in ages though Dec 20 13:31:38 sysfs says 47800 cpu_thermal Dec 20 20:22:35 anyone here know if I can write to the EEPROM from the OS? Dec 20 20:22:49 when I try to do it via sysfs it just doesn't write anything Dec 20 20:22:58 i2cset says "device busy" Dec 20 20:23:20 I can read the contents of the eeprom via sysfs just fine Dec 20 22:50:32 TonyTheLion: you can write it via sysfs just fine, but the eeprom is write-protected by default Dec 20 22:51:44 since it contains the factory-programmed board identification that's used by the bootloader, so if you make a mistake when writing it you'll end up with a board that's a bit tricky to recover Dec 20 22:52:10 lifting the write-protection is done by connecting a certain testpoint on the board to ground Dec 20 22:53:58 zmatt: thanks :) **** ENDING LOGGING AT Fri Dec 21 03:00:02 2018