**** BEGIN LOGGING AT Mon Sep 14 02:59:58 2015 Sep 14 05:12:36 hi guys, is thre already infomation out there about the pinout of the x15 expasion headers? Sep 14 05:40:23 <_zeekHuge> hey ! I wish to access the ADC on BBB board using PRUs, how to get started ? Sep 14 05:44:15 _zeekHuge: I directly access it from userspace in linux, which is essentially similar (but without low-latency irq handling available) Sep 14 05:44:21 it's not actually hard to setup the adc Sep 14 05:47:16 one thing to avoid however: don't edit an enabled step. In fact before I reconfigure the adc I disable all steps and wait until the FSM is idle (status == 0x10) Sep 14 05:48:01 violating that rule led to a locked-up FSM (and note that the ADC module doesn't have a local reset, so then it's reboot time) Sep 14 05:49:09 _zeekHuge: in fact, you probably just want to get the ADC *data* to the PRUs, in which case I'd do ADC setup from linux Sep 14 05:50:22 if properly set up, PRU can get an irq whenever the ADC fifo reached some threshold limit and then it can simply read the values directly from the ADC fifo Sep 14 05:51:07 or you can have EDMA deliver the data into PRUSS local ram and then notify the PRU cores about it Sep 14 05:51:35 what is a usecase for ADC access from the PRU? Sep 14 08:27:11 Hi, actually writing a driver for a DAC using SPI1 on the BBB, my driver load correctly (modprobe return no error) but ls /sys/bus/iio/devices/ is empty no device listed in Sep 14 08:28:16 This is my driver code : http://hastebin.com/egicajevuq.coffee Sep 14 08:30:33 do you have that in readable? Sep 14 08:30:36 like white on black Sep 14 08:30:43 or black on white? Sep 14 08:30:47 not gray on gray Sep 14 08:31:25 http://pastebin.com/ndhQYKRL Sep 14 08:41:01 Did you found anything missing that can explain the empty iio dir ? Sep 14 08:44:38 maybe you need .attrs? Sep 14 08:45:22 Oh ==' stupid mistake, I didn't updated my devices tree, so no match >.< this work now i've the iio:device0 Sep 14 08:45:50 :) Sep 14 08:51:52 hum but no out_voltage0 in the sysfs .. :/ just have the dev name power subsystem uevent of_node Sep 14 09:14:33 Well this work i've out_voltageX_raw, but I think my driver is missing something related to regulator and voltage input for the chip dac124S05, but I've some trouble undestanding this part of the driver, the chip VREFIN pin is connected to VADC on the BBB of should I define the driver to have the out_voltage_scale ? something is needed in the device tree ? or is it the regulator thing in the driver ? Sep 14 09:15:32 what should I * Sep 14 09:18:05 VREFIN is connected to VDD_ADC * Sep 14 09:20:27 Is the ldo3_reg in the device tree related to the 1.8V output on VDD_ADC ? Sep 14 09:29:02 Any idea ? :/ Sep 14 11:11:17 How do install Debian on beaglebone black Sep 14 11:11:20 ? Sep 14 11:11:26 any link? Sep 14 11:13:44 beagleboard.org Sep 14 12:52:26 Hi, i'm writing a driver for the DAC124S085, my spi device is actually sending the 16bits sequence but splitted in two 8bits word, i've set spi->bits_per_word to 16 but this doesn't change .. why ? (reading the value from spi device return 16 so the value is correctly set) Sep 14 12:56:15 Any idea where this can come from ? Sep 14 12:56:21 i'm using linux/spi/spi.h Sep 14 13:20:09 what the heck is this? http://eu.mouser.com/ProductDetail/BeagleBoard-by-CircuitCo/999-0004285/?qs=sGAEpiMZZMvNM%2fd3q5fCVx%2f6B2iVdXWNQKMnFaJoIjI%3d Sep 14 13:20:30 can't seem to find any details Sep 14 14:27:44 Hi, using linux/spi lib, spi_write() takes about 355us to processed, the sequence need 1us to be sent, what's is taking so long to the spi_write function and how I can reduce this huge time ? Sep 14 14:28:33 commenting the spi_write function the write_raw call takes 3us ... the 350us comes from the call to spi_write() Sep 14 14:30:01 pastebin the driver code Sep 14 14:35:10 http://pastebin.com/3v3CVZMn Sep 14 14:44:14 av500: did you find anything ? :/ Sep 14 15:00:19 samael: Looks like a plain old BBB, despite the "Industrial" label. Sep 14 15:00:30 Gwak: what does sysfs print for the spi driver "name"? Sep 14 15:01:59 it's a driver I just wrote for the dac124s085 Sep 14 15:02:03 it print dac124s085 Sep 14 15:02:28 180us of duration with processor at 1Ghz Sep 14 15:02:51 Ragnorok: yep. but how can it cost two times an ordinary bbb revC then? Sep 14 15:02:53 but this still very huge for a sequence of 1us .. Sep 14 15:03:03 Got me there. Sep 14 15:04:11 samael: Might email them and see what they say. And ask why no datasheet? (grin) My xp is Mouser is usually pretty good about datasheets. Sep 14 15:05:10 it's marked as new product (in their stock), maybe docs will come soon Sep 14 15:05:29 (for various degrees of "soon") Sep 14 15:07:12 Gwak: no Sep 14 15:07:18 Gwak: I mean what SPI driver does it use Sep 14 15:07:44 indio_dev->name = spi_get_device_id(st->spi)->name; Sep 14 15:11:34 That's what I said it return dac124s085 Sep 14 15:12:09 I'm using the spi Sep 14 15:12:13 device tree : http://pastebin.com/7Hb5VLJR Sep 14 15:12:35 spi1 * Sep 14 15:13:04 indio_dev->name = "dac124s085" Sep 14 15:14:31 something is wrong ? Sep 14 15:16:27 and looking at the scope you really see the 24mhz? Sep 14 15:16:29 spi clock Sep 14 15:16:38 Ye Sep 14 15:18:29 Like I said it take a bit less than 1us to send the 16bits word Sep 14 15:18:34 700ns exactly Sep 14 15:18:42 and the clock is at 24Mhz Sep 14 15:19:05 650ns * Sep 14 15:19:14 650ns * Sep 14 15:24:38 To trace the fonction i'm using ftrace, doing echo XXX > out_voltage0_raw, ftrace duration of dac124s085_write_raw shows ~180us Sep 14 17:12:26 Hey... when I'm flashing, it doesn't seem to matter whether or not I hold down S2. Lights flash the same either way Sep 14 17:12:50 is that normal? That the SD card starts flashing the EMMC even when you start up without S2 held down? Sep 14 17:28:43 depends on the boot script of the bootloader on eMMC Sep 14 17:29:02 I think it will try the SD card if eMMC doesn't look bootable Sep 14 17:38:05 ok... How can I tell if an image is bootable or a flasher? I'm working with an erle-brain and their images are named very confusingly Sep 14 17:42:03 foobarbecue, "bootable" depends on the u-boot flashed to the eMMC... "flasher= eMMC-flasher in file name.."... Sep 14 17:42:17 if it comes from rcn-ee.net, it'll be "bootable". .;) Sep 14 17:42:29 (i have no time for silly push buttons.. ;) ) Sep 14 21:24:13 OK I am having a bizarre GPIO problem Sep 14 21:24:55 Trying to poll a GPIO1 pin from the PRU, reading the memory address directly (0x4804C138) Sep 14 21:25:31 Reading that address with devmem2 yields the expected value, where the appropriate bits are toggled depending on the status of the line Sep 14 21:25:41 but when I read it with the PRU, those bits are always low Sep 14 21:25:49 BUT the other bits in the register match Sep 14 21:27:05 devmem2 toggles between 0x260D7300 and 0x360DF300 as expected, pru always comes back with 0x260D7300 Sep 14 21:27:40 anyone have any ideas? Sep 14 22:50:19 Hi, can someone point me to an ISO for t bb black thats extreamly small Sep 14 22:56:46 thanks for your outstanding support as eva Sep 14 22:59:44 byeee lol Sep 15 01:24:50 What cool projects can I do with my BBB? Sep 15 01:28:39 Hi Colin Sep 15 01:29:01 And hello to you, Stefan Sep 15 01:29:16 Is anyone here? Sep 15 02:53:06 Ello? **** ENDING LOGGING AT Tue Sep 15 02:59:58 2015