**** BEGIN LOGGING AT Mon Dec 17 03:00:01 2018 Dec 17 03:06:27 Aw! Dec 17 03:41:07 So launching something might be a bit difficult. If you want to do interplanetary type stuff you have to shield your electronics a lot and use stuff that doesn't die easily. They have to shield stuff immensely I've heard. Dec 17 03:42:06 and use radiation-hardened electronics presumably Dec 17 03:49:51 unfortunately that can be quite expensive so high reliability and heavy shielding has taken place instead. Silicon on Saphire I hear works well. If they use silicon carbide the temperature issues are less of a problem etc. Dec 17 03:52:12 I guess enough shielding negates the need for rad-hard Dec 17 04:18:59 Hey! Dec 17 04:19:24 No space. Dec 17 04:20:02 Just, maybe a reasonable (super-powerful) vacuum that can be WiFi controlled online via website. Boy! Dec 17 04:20:14 Mowers and vacuums! Dec 17 04:21:15 "Please sign in. This way, your vacuum knows your password and credentials." Dec 17 04:21:43 Hey...this person bought me a vacuum w/ WiFi on it. Ha! Dec 17 04:22:29 It sucks and can be controlled at distances up to 15 ft. Hahhahaah. Dec 17 04:23:30 I guess I can put something together but not for mass production. Dec 17 04:25:11 for instance, a BBB powered house vacuum. Add the filter and boom! Production! Sometimes the house gets stuffy. Dec 17 04:25:43 ... Dec 17 04:26:59 I mean they sell those fans w/out filter for enormous amounts of money. Why not have a BBB fan w/ filter that is portable? Seems reasonable enough. Aw! Who knows? Dec 17 04:28:09 BBB blower fan w/ filter! Cha-ching. Dec 17 04:29:00 Okay...I will make it and make it available. Dec 17 04:29:38 But! I am not making the motor. Who wants to make the motor? Dec 17 04:32:17 I mean...I tried to make a makeshift fan-filter combination that would suck up all the old dust from the previous owner. Dusty chum, he/she was. Anyway...now I am getting dusty. Any motor mfg. our there? Dec 17 04:32:45 our = out Dec 17 04:34:23 Okay for now...bbl. On break. Dec 17 06:03:42 monolog man Dec 17 14:44:07 Hello everyone, I am new for Beaglebone black wireless, and meet a problem that "no space left on device ". Who can help me? Dec 17 14:44:32 more context please Dec 17 14:46:34 Filesystem Size Used Avail Use% Mounted on udev 215M 0 215M 0% /dev tmpfs 49M 6.1M 43M 13% /run /dev/mmcblk1p1 3.5G 3.3G 25M 100% / tmpfs 242M 0 242M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 242M 0 242M 0% /sys/fs/cgroup tmpfs 49M 0 49M 0% /run/user/1000 Dec 17 14:47:00 I use df -h Dec 17 14:47:17 what firmware is this? Dec 17 14:47:22 what were you doing? Dec 17 14:47:47 what are you trying to achieve with the device? Dec 17 14:47:52 no Dec 17 14:48:00 I just install some package. Dec 17 14:48:50 When I use apt-get install xxx , I got the error message. Dec 17 14:49:20 ok, so what are you trying to achieve with the device? Dec 17 14:49:32 Jack__: well the message is pretty clear. your flash memory is full, so, you cannot install anything. solution: uninstall something. Dec 17 14:50:20 I want to use this board to build up a mesh network. Dec 17 14:50:35 right, then you probably don't need all the graphical user interface and such Dec 17 14:50:52 start from an IoT image, flashing latest is a good idea anyway Dec 17 14:51:18 Ok, so I need to update the lastest kernel. Dec 17 14:51:27 image Dec 17 14:53:44 Thank you tbr and <@LetoThe2nd> Dec 17 14:55:16 np Dec 17 15:48:25 m Dec 18 00:35:26 Hello! I have X15 BB. I need to use I2C to talk to Adafruit-SHT31-Sensor. Could anyone help me in getting started? Dec 18 00:45:34 Hold on. Let me look up the idea. Dec 18 00:46:52 https://learn.adafruit.com/adafruit-sht31-d-temperature-and-humidity-sensor-breakout/python-circuitpython is something I just found. Dec 18 00:47:05 Do you want to use Python? Dec 18 00:48:02 Ut Oh. x15...please hold. Dec 18 00:49:36 https://elinux.org/Beagleboard:BeagleBoard-X15 is another source I found. Do you have your connection yet or do you need to make your connection still? Dec 18 00:53:14 I am at very zero point. I need to make a connection. I also need to find out GPIO pins for I2c Dec 18 00:53:58 Okay. I have the SRM now. I will look for the i2c connections. Dec 18 00:54:47 Thanks! Dec 18 00:56:26 p. 62 states that i2c is a shared bus. It seems there is already a tmp102 sensor on this board. Dec 18 00:56:50 but that is i2c1 on this board. Let me see if there is another one. Dec 18 00:59:29 https://github.com/beagleboard/beagleboard-x15 is another source for details. Dec 18 01:03:06 dreamhiker: I think I am falling short on this board function idea, really. I found that i2c is listed w/ specific already-shared devices. Dec 18 01:03:44 That is all for now. Maybe a I/O pin from those specific connectors will do? I will have to check the schematic. Dec 18 01:07:59 I see the UART section of this board is taken away b/c of the FTDI cabling pins. Dec 18 01:10:22 dreamhiker: You may want to look into another board for i2c (if this is truly want you need) or stick around. I am sure people have made some work around (take this, give that) for the board. Dec 18 01:11:01 I have not gotten to the expansion headers just yet in the SRM. But, I do see that there are specific header connectors. Dec 18 01:16:57 I mean...there is a section showing, in the SRM, i2c1 and this can be "modified" if you can write to the am572x (I am guessing). Dec 18 01:16:57 ... Dec 18 01:16:59 Dang it. Dec 18 01:18:33 If you want to try the TRM of that chip, I am sure that there is a way to use assembly w/ ARM arch. to change things up. I would not do this task, though. It would be years in the making. I am more of a nuisance. Dec 18 01:21:28 http://www.ti.com/lit/ds/symlink/am5728.pdf is not that much of a whopper but it will be trying if you want to take on this task. Dec 18 01:24:35 There is a TRM, though. It will be more in depth and have better info. Dec 18 01:28:01 sorry...that ti.com link is the TRM. Dec 18 01:38:05 in the TRM, there is a pinmux utility I found on page 405. It may help you. Dec 18 01:45:08 I think I may have found something. On page 369, there is a couple pru pins capable of producing uart functionality. Dec 18 01:45:55 Now, if the dog-gone schematic was in .pdf, I could search the contents to see the pru_pins they have listed. Dec 18 01:46:22 ... Dec 18 01:46:32 dreamhiker: Are you still there/here? Dec 18 01:46:59 Sorry. Dec 18 01:47:07 No issue. Dec 18 01:47:33 Did you get to read any of that garbled mess I just typed out? Dec 18 01:47:36 what document are you refering to? Dec 18 01:48:07 the SRM of the board (x15) and the TRM of the chip (am5728). Dec 18 01:49:11 TRM is http://www.ti.com/lit/ds/symlink/am5728.pdf? Dec 18 01:49:18 dreamhiker: using the expansion headers on the x15 is a fair bit of headache Dec 18 01:49:45 Hello zmatt? Dec 18 01:49:56 zmatt knows more than I do. Dec 18 01:50:00 dreamhiker: if you just need i2c, best would be to check which pins are already configured for i2c use by default (u-boot will configure the pins for the configuration intended for the am572x evm lcd board) Dec 18 01:50:06 Thank you for your previous help! PWM is working fine Dec 18 01:50:34 ah I've helped you before. sorry I'm terrible with names Dec 18 01:50:45 Thanks Set! Dec 18 01:50:59 are you using my patched u-boot or still the stock one? Dec 18 01:51:03 No issue. I thought I would chime in until the ultimate timeout. Dec 18 01:51:17 zmatt, how do I start? Dec 18 01:52:07 Do I already have all the drivers? Dec 18 01:52:36 Is it done like PWM (through the pseudo file-system)? Dec 18 01:52:51 yes of course you have the drivers, there's already at least one i2c bus operational on the board (though not necessarily on the expansion header) Dec 18 01:52:51 Do I need to configure pins? Dec 18 01:52:56 are you using my patched u-boot or still the stock one? Dec 18 01:53:51 I can switch to your u-boot if needed, as long as you give me instructions on switchng Dec 18 01:54:27 Allow me to ask again, why yours is better than the default one? Dec 18 01:54:56 it isn't "better", I just need to know which one you're using Dec 18 01:55:27 the default one configures expansion header pins for the functions used by the am572x evm lcd board Dec 18 01:55:35 mine leaves the expansion header pins unconfigured Dec 18 01:55:45 Dang...I just found the .pdf schematic! Dec 18 01:56:02 officially you're supposed to build a custom u-boot for your desired pin configuration Dec 18 01:56:47 though for some pin functions you can mostly get away with doing the pin configuration in DT, pwm for example Dec 18 01:57:08 Could you send me a reference to building u-boot? Dec 18 01:59:38 Dang...custom u-boot for pin configuration. That sounds nifty. Dec 18 01:59:57 set_: if you "nifty" you mean "annoying and inconvenient as fuck" Dec 18 02:00:00 *if by Dec 18 02:00:11 I nifty if by. Dec 18 02:00:13 Ha! Dec 18 02:00:18 I understand. Dec 18 02:00:21 Sorry. Dec 18 02:00:28 set_: the only reason it is being done there instead of in DT is due to chip errata Dec 18 02:00:35 Oh. Dec 18 02:00:42 Updates! Dec 18 02:01:03 They made some mistakes? Dec 18 02:01:12 doing pin configuration at a later point in boot can cause glitches of significant length on the pins Dec 18 02:01:44 Oh...see! I do learn stuff. Cool but depressing/aggravating. I get it now. Dec 18 02:02:16 zmatt: I am thinking this errata was not present when the board was intro'd. Dec 18 02:02:19 also, accessing iodelay configuration shoudl be done when there's no other traffic on the l4 interconnect the iodelay module is connected to, otherwise the whole bus may lock up Dec 18 02:02:34 Yikes. Dec 18 02:03:01 the glitches during reconfiguration have been known for quite a while I think Dec 18 02:03:25 Oh. This is the first I heard of it. I am an ole timer now, I guess. Dec 18 02:03:35 "out of the loop" Dec 18 02:04:16 Anyway...I will not interrupt any longer. I am sure you and dreamhiker have many tasks to deploy. Dec 18 02:04:49 the iodelay lockup is a far more recent discovery, in fact it has the highest erratum number in the latest errata document of the am572x Dec 18 02:05:32 dreamhiker: lemme check if I have u-boot prebuilt already Dec 18 02:05:59 though actually, as long as you only need i2c and pwm it may actually be simpler to keep the default config Dec 18 02:07:19 at some moment I will need SPI Dec 18 02:08:30 zmatt, so how do I start? Dec 18 02:10:40 dreamhiker: if you haven't already, could you install the bbx15 version of my show-pins script: https://github.com/mvduin/bbb-pin-utils/tree/bbx15-experimental#show-pins Dec 18 02:10:49 and then pastebin the output of: sudo show-pins | sort Dec 18 02:11:10 just to check what the default configuration looks like really Dec 18 02:17:04 zmatt: I got what you were saying. It is inconvenient to make an entire u-boot available. I remember trying. I failed and moved on. Dec 18 02:17:37 "make available" ? Dec 18 02:17:58 To have a booting board w/ a kernel! Dec 18 02:18:28 That is what u-boot is for, right? Dec 18 02:18:29 https://pastebin.com/QDSDK6gN Dec 18 02:18:52 for specific processes to take place before the kernel kicks in? Dec 18 02:19:31 dreamhiker: ew, sorting it by expansion header pin was clearly a mistake. I guess it would have looked better without the sort Dec 18 02:19:57 let me redo Dec 18 02:20:15 redo! Dec 18 02:20:23 but ok, definitely no pins configured to spi by default Dec 18 02:20:52 lot of pins used for video in/out Dec 18 02:22:11 https://pastebin.com/8jgpb7Y4 Dec 18 02:22:54 yeah, definitely clearer Dec 18 02:23:33 so anyway, this shows your current pin configuration, mostly done by u-boot except P18.12 has been reconfigured by your customized DT Dec 18 02:24:02 it does include two i2c buses, but no spi Dec 18 02:30:05 what are those? Dec 18 02:31:40 you don't see them in the output? i2c-3 on P17.53/46 and i2c-4 on P18.03/04 Dec 18 02:34:37 I do see now :) It was not grep-able Dec 18 02:38:26 yeah sorry about the ² Dec 18 02:39:17 :) it is cute Dec 18 02:41:59 Now, what do I do to manipulate those? Dec 18 02:47:02 the i2c buses? first you'll need to enable them in DT. if you have i2c devices with a kernel driver then you'll need to declare those too, but if you just want to poke at devices directly from userspace using the i2c-dev interface then enabling the bus suffices Dec 18 02:47:45 beware that they'll be called &i2c4 and &i2c5 in DT Dec 18 02:47:54 (off-by-one numbering -.- ) Dec 18 02:49:03 as a reference example, here's the declaration for the i2c-2 bus (which is local to the bbx15 and not on any expansion header): https://github.com/RobertCNelson/dtb-rebuilder/blob/4.14-ti/src/arm/am57xx-beagle-x15-common.dtsi#L428-L442 Dec 18 02:49:56 setting status="okay" will enable the bus (by overriding a previous status="disabled" declaration), it then sets the bus clock speed, and it declares one i2c device that has a kernel driver, namely an rtc Dec 18 02:51:57 Thank you zmatt! I will continue tomorrow. Dec 18 02:52:01 so for example a minimal declaration would be something like &i2c4 { status = "okay"; clock-frequency = <100000>; }; Dec 18 02:52:35 to make /dev/i2c-3 show up **** ENDING LOGGING AT Tue Dec 18 03:00:00 2018