**** BEGIN LOGGING AT Thu Oct 13 02:59:59 2016 Oct 13 07:15:09 When I converted from the old 3.8 to 4.4 kernel my PRU overlay is not Oct 13 07:15:19 working anymore.. Anyone know any specific differences? Oct 13 07:18:52 it looks like current default device trees no longer include the stuff needed for either uio-pruss or rproc, presumably leaving the choice to an overlay Oct 13 07:18:52 https://github.com/RobertCNelson/linux-stable-rcn-ee/blob/4.4.19-ti-r41/arch/arm/boot/dts/am335x-boneblack.dts#L16 Oct 13 07:18:52 (or custom main dts) Oct 13 07:19:00 note both includes being commented out Oct 13 07:28:48 zmatt: I have already done this and I now have uio_prussdrv in lsmod Oct 13 07:28:49 http://pastebin.com/MTcabBB3 Oct 13 07:29:12 ok, the kernel loading the driver is a good sign Oct 13 07:29:18 the only error I have is: pruss_uio 4a300000.pruss: No children Oct 13 07:29:24 ah that stupid error again Oct 13 07:29:45 has anything changes in how you should compile the .dts files? Oct 13 07:30:13 no the driver moronically fusses about something it shouldn't fuss about Oct 13 07:30:43 I've solved this one before but don't remember the solution off-hand... probably it can be dug up using google Oct 13 07:30:58 alternatively you can check the driver source code, iirc it was pretty evident what it's crying about Oct 13 07:32:51 in fact "pruss: no children" is probably a pretty specific thing to search for Oct 13 08:04:29 pruss - not for children Oct 13 08:19:03 heh :D Oct 13 08:19:50 Still cant find a solution to the problem.. I now get segfault at prussdrv_pru_enable_at Oct 13 08:30:41 and there seems to be a problem with my .dts file from 3.8.. Something has changed in how dts files are written from 3.8 to 4.4 Oct 13 08:40:39 nothing has been changed about how dts files are written in general afaik Oct 13 11:34:18 zmatt: Got it working now by adding the pins in the pru-fragment in the DTS file.. Oct 13 11:49:55 hi Oct 13 11:50:21 i am beginner to beaglebone black Oct 13 11:50:35 i need to start from basic Oct 13 11:50:40 can u help me Oct 13 11:50:45 hey Oct 13 11:51:42 hello Oct 13 11:55:39 Praveen, you need to be more specific... Oct 13 11:56:33 i am beginner to beaglebone Oct 13 11:56:50 just phrase your question Oct 13 11:56:56 i need to start from first Oct 13 11:57:30 can u send and books or link for how to install and how to write code Oct 13 11:58:06 Hello , I am using ftdi usb to serial module to connect device using usb to serial converter. I wrote one rule to run application when device plugged in. Initially i get garbage data while application run and than later application works properly. Oct 13 11:58:21 Any one had face this issue?? Oct 13 11:59:10 device runs with 115200 8N1 configuration Oct 13 12:20:29 kk_: are you using the debug port? Oct 13 12:20:40 kk_: if so, you get first all the boot up stuff Oct 13 13:29:26 @KotH : No USB port Oct 13 13:31:07 kk_: then i dont know Oct 13 13:31:20 kk_: garbadge in your usb gadget app's buffer? Oct 13 13:36:00 it there any way that we can clear it Oct 13 13:36:01 ? Oct 13 13:37:53 I have configured port with following configuration. Oct 13 13:37:56 struct termios tty; int parity = 0; int status = 0; memset (&tty, 0, sizeof tty); if (tcgetattr (fd, &tty) != 0) { printf("error %d from tcgetattr", errno); return errno; } cfsetospeed (&tty, 195200); cfsetispeed (&tty, 195200); tcflush(fd, TCIFLUSH); tty.c_cflag &= ~CRTSCTS; tty.c_iflag &= ~IGNBRK; tty.c_lflag = 0; tty.c_oflag = 0; tty.c_cc[VMIN] = 0; tty.c_cc[VTIME] = 5; tty.c_iflag &= ~(IXON | IXOFF | IXANY); tty.c_cflag |= Oct 13 13:41:23 did you make sure there's no getty enabled on that port? Oct 13 13:42:21 also don't try to paste code here, use pastebin or hastebin or whatever-is-your-favorite-bin Oct 13 13:45:19 There is no getty configured for that port Oct 13 13:46:08 ftdi_sio 53248 1 usbserial 53248 3 ftdi_sio Oct 13 13:46:28 this two modules loaded when i plug USB Oct 13 17:24:03 Hi folks, I am a beginner here, need some help for interfacing SMBus based device with BBB Oct 13 17:25:02 Can you please have a look http://stackoverflow.com/questions/40027156/device-interfacing-using-smbus-on-beaglebone-black Oct 13 17:26:09 ITYM I²C Oct 13 17:28:02 Its SMBus but compatible with I2C Oct 13 17:30:02 Datasheet never mentioned about I2C, it only contains "SMBus" as communication protocol. Everywhere SMBus throws results for I2C. http://www.mouser.com/ds/2/308/ADM1032-D-106508.pdf Oct 13 17:30:42 SMBus is essentially I²C, IIRC Oct 13 17:30:43 I googled a lot but everywhere SMbus returns pages for I2C Oct 13 17:31:48 Yeah. Can you please have a glance at the question ? http://stackoverflow.com/questions/40027156/device-interfacing-using-smbus-on-beaglebone-black Oct 13 17:32:10 and the sensor is powered on? Oct 13 17:32:23 Yes. +3V3 Oct 13 17:32:26 the signal levels are compatible? Oct 13 17:32:47 Common ground with BBB at P9.0 Oct 13 17:32:53 Yes Oct 13 17:35:24 someone who actually uses i2c on the bbb should comment on that Oct 13 17:43:56 Please do Oct 13 17:50:24 Hi People Oct 13 18:20:25 hiya Oct 13 19:41:03 hmz, getting consistent freezes with xorg-video-fbturbo on a 4.8-bone kernel... and inconsistent ones with xorg-video-fbdev Oct 13 20:30:23 Hi I am Anshul Singhal. I am new to beagleboard. I want to start contributing in beagleboard. Can you guys please help me for the same? Oct 13 20:36:42 clearly not Oct 14 02:32:52 What book(s) are you reading? **** ENDING LOGGING AT Fri Oct 14 02:59:58 2016