**** BEGIN LOGGING AT Tue Dec 13 03:00:01 2016 Dec 13 07:49:40 I configure one of my GPIO pins (GPIO2[5]) in device tree as PIN_OUTPUT_PULLUP. After the system is booted I see the pin being logic low. pinmux-pins reports it as: pin 36 (44e10890.0): 44e10800.pinmux (GPIO UNCLAIMED) function pinmux_gpio_pin group pinmux_gpio_pin Dec 13 07:50:38 When I use &gpio2 { ti,no-reset-on-init; } it's pulled high after boot Dec 13 07:51:09 But I don't want to prevent the gpio controller from getting reset, how do I prevent this? Dec 13 09:34:16 I want to write a structure in EEPROM (4KB)of BBB. But I dont have any idea from where to start. please help me with this. Dec 13 09:35:02 can anyone suggest me how to read/write from/to BBB EEPROM Dec 13 09:36:14 anky: like to/from any other eeprom? /sys/bus/i2c/devices/0-0050 probably Dec 13 09:37:07 anky: in there is a file named eeprom. Dec 13 10:03:11 help me out with reading and writing into EEPROM of BBB Dec 13 10:10:14 anky: i already answered your question. what was unclear about it? Dec 13 10:21:00 LetoThe2nd: can i have some reading material from which i can basics clear...actully i am willing to write a data structure in BBB EEPROM.. Dec 13 10:21:33 I am new to it..so ..thank you Dec 13 10:26:37 anky_: well it is a file that you can open, read and write. Dec 13 10:26:58 anky_: so there is no more to it than basic posix file operations. Dec 13 10:28:09 may be i have to do this using i2c Dec 13 10:28:28 anky_: no, you do not. the driver is there and ready to take care of that for you. Dec 13 10:28:46 thats the whole point of operating systems and their drivers. Dec 13 10:29:22 so concerning documentation, pick your favorite book or document on file operations in c. Dec 13 10:29:45 so you mean like simple open,read,write ..as we use for simple file Dec 13 10:30:01 you can even try and debug with a standard file, and switch over to the eeprom once you are finished. Dec 13 10:31:23 ok. let me try this...thank you... Dec 13 13:05:21 I am trying to boot my BBB off my microsd card by default. I saw this guide http://elinux.org/Beagleboard:Updating_The_Software#Image_For_Booting_From_microSD Dec 13 13:06:12 I can't find the MLO file, and I understand that newer BBB don't have the file Dec 13 13:06:24 Fwiw, i am using a BBB industrial Dec 13 13:07:22 But i believe that isn't too much of an issue Dec 13 13:08:51 s/issue/difference/ Dec 13 15:54:34 Hello together Dec 13 15:55:17 i followed this description Dec 13 15:55:19 http://www.thomas-wedemeyer.de/beaglebone-canbus-python.html Dec 13 15:55:37 with the same parts Dec 13 15:56:34 and now i try to meassure at p9 pin 24 against ground and it doesnt work with the command cansend Dec 13 15:57:14 what do i wrong or what i have to consider ? Dec 13 16:00:25 can no one help me ? Dec 13 17:07:22 Is EQEP support for BBB fixed ? Dec 13 17:08:08 I want to contribute to BBB linux kernel just for my free time. Dec 13 17:08:25 Any project ideas ? Dec 13 20:17:17 eqep works fine :P Dec 13 22:04:03 Hello. I have a BeagleBoard-xM, and recently a strange thing started to happen: on the serial console, some of the characters displayed were corrupted, and then after a few seconds, an endless stream of 0xff bytes started appearing. Dec 13 22:06:19 I powered down the board, verified MLO and uboot checksums on the SD card, then booted it up again, but stopped at the uboot prompt. I was hoping to do a memory test, but suddenly the endless stream of 0xff's appeared in the output again Dec 13 22:07:10 also, had a few situations, where the serial port changed speeds spontanously Dec 13 22:09:07 btw. the temperature reported by /sys/class/hwmon/hwmon0/temp1_input was sth like 79 Celsius (79000) Dec 13 22:10:36 I tried to leave the board unpowered for a while, and then boot to uboot prompt again, but every time, after a while, the stream of 0xff's appeared Dec 13 22:19:35 Help Dec 13 22:20:11 How to setup the correct cross compile environment for Beaglebone Dec 13 22:20:33 in ubuntu machine. Dec 13 22:23:03 I used the latest build image from the official beagle bone site to boot my beagle bone. I downloaded the kernel and compiled it on Ubuntu machine, when i cross compile the driver and a user code which uses the driver to send data on GPIO pins. The code crashes saying an issue Dec 13 22:24:20 My question is, how to get the correct kernel to cross compile the driver on a local ubuntu machine Dec 13 22:24:50 right now my beagle bone uses 4.4.30-ti-r64 Dec 13 22:25:17 any suggestions please Dec 14 02:23:19 Wolf480pl: hmm Dec 14 02:23:51 0xff means it saw a start bit (i.e. a pulse of sufficient width) but nothing more than that Dec 14 02:26:45 * zmatt goes to look for the schematic to see if he happens to spot anything of interest Dec 14 02:37:51 serial port changing speed... at login prompt by any chance? getty cycles through a few common speeds in response to a break signal Dec 14 02:43:37 ok, I actually have no idea... serial port interfacing looks okay at first sight. afaict no BBB-style power domain violation that could have slowly assaulted the port over time... although your symptoms don't match anyway since I'd expect a dead rx pin, not misbehaving tx **** ENDING LOGGING AT Wed Dec 14 02:59:59 2016