| 00:53 | 6JTAAE6RO | Hi everyone |
| 00:53 | 6JTAAE6RO | Why help me with cubox 1st generation?? |
| 00:57 | 6JTAAE6RO | ? |
| 00:59 | cbxbiker61 | just ask the question |
| 01:16 | djwatt3_ | I have installed geexbox 3.1 on cubox 1st... Now i need to download add-on, and I need to buy dvb-sat and dvb-dtt device to transform cubox in digital tv receiver |
| 12:39 | MarcusVinter | join ##security |
| 13:20 | jnettlet | AA review of the CBi is up. https://www.youtube.com/watch?v=J4Ty-YqbGAo |
| 15:49 | crazystick | hello, i was wondering if anyone has been able to use the 1-wire kernel driver on the hummingboard |
| 15:50 | crazystick | I was hoping to connect as DS18B20 but nothing shows up under /sys/bus/1w/devices |
| 15:50 | crazystick | I'm guessing more dts changes required? |
| 15:54 | dz0ny | diy you tried loading module manually? |
| 15:54 | dz0ny | aka modprobe module_name |
| 15:56 | crazystick | yeah, the modules are loaded, and I have the /sys/bus/w1 |
| 15:56 | crazystick | but no devices show up |
| 15:58 | crazystick | the wiki doesn't have a label for 1-wire on the header layout |
| 15:59 | crazystick | but i tried plugging the signal into all the gpio pins |
| 16:35 | jnettlet | crazystick, the W1 GPIO driver works on the HB |
| 16:35 | jnettlet | but you will need to add a device-tree entry for it |
| 16:37 | crazystick | do you know where I can get such an entry? or do I have to write one? |
| 16:38 | dz0ny | get the kernel edit config and build dbt |
| 16:48 | crazystick | sorry dz0ny, I don't know what you mean. I know how to build a kernel, but I already have the drivers 1w-gpio and 1w-therm |
| 16:51 | crazystick | jnettlet - I think you are saying that something has to be added to imx6qdl-hummingboard.dtsi (which then has to be compiled to a dtb file) correct? |
| 16:57 | jnettlet | crazystick, one sec I will give you a test patch |
| 17:00 | crazystick | great - standing by |
| 17:03 | johnwalkr | dts will be really cool in like 5 years |
| 17:03 | johnwalkr | it's been a rough ride using it for the last year or so |
| 17:05 | jnettlet | johnwalkr, we said the same thing 3-4 years ago when it was first gaining acceptance and we were doing the initial implementation for the XO-1.75 |
| 17:06 | johnwalkr | might take 10 years then ;) |
| 17:06 | johnwalkr | my experience is with beaglebone black which has switched in the last year to device tree |
| 17:06 | Defiant | no dto support on hummingboard? |
| 17:06 | johnwalkr | so i kind of assumed it was only around for a year or 2 |
| 17:07 | jnettlet | it is supported, we just export all the GPIO pins as gpios |
| 17:07 | jnettlet | johnwalkr, device-tree actually comes from openfirmware and solaris. |
| 17:08 | jnettlet | it was adopted by linux to help manage ARM code duplication for all the different machines |
| 17:08 | johnwalkr | i didn't realize the history from solaris |
| 17:09 | johnwalkr | i know the history of it in linux |
| 17:10 | jnettlet | yep I worked with Mitch Bradley at OLPC who was one of the original creators of device-tree |
| 17:13 | johnwalkr | it's really cool, it's just that other solutions and it were both in so much flux that it's surprisingly hard to do a google search and land in a place that will teach it to you |
| 17:15 | johnwalkr | plus it's just confusing because there can be multiple places to edit to get the desired result. but again this is BBB experience talking, I haven't actually turned my hummingboard on yet |
| 17:16 | johnwalkr | It was just the only SOM that had all the signals routed that I need for my application |
| 17:21 | crazystick | I am by no means an expert in device drivers, and I'm just learning about the device-tree now. is there some way to load additional things into the device-tree of a running kernel? |
| 17:24 | jnettlet | crazystick, nope not yet. there has been some talk about it. |
| 17:24 | jnettlet | basically the idea is device-tree describes the hardware so "in theory" it shouldn't change while the kernel is running |
| 17:32 | crazystick | I guess though that its not always true - I'm only guessing here, but couldn't some of the pins on the HB header be dual purpose? |
| 17:33 | crazystick | I was following some tutorial for the DS18B20 on the raspberry pi, which uses GPIO 4 for 1-wire but if that pin is configured for 1-wire, does that mean it can't be used as a GPIO? |
| 17:33 | johnwalkr | yeah and if i am not mistaked you can change pin mux on the fly? |
| 17:33 | jnettlet | yes |
| 17:34 | jnettlet | but in remuxing pins you are actually changing the hardware layout |
| 17:40 | jnettlet | crazystick, give this a try. http://pastebin.com/Wqq5LqQN That should make pin 7 a 1-wire master |
| 17:41 | jnettlet | if it works and you don't mind sharing your success on the community forums I would appreciate it |
| 17:42 | jnettlet | I will think about how this can be added to wiringX to make this process easier |
| 17:43 | jnettlet | we may want to break out each gpio pin to be their own device-tree entry |
| 17:45 | mk01 | I gave away what |
| 17:45 | mk01 | (wrong window) ... |
| 17:53 | jnettlet | mk01, small parts of your soul. bit by bit, byte by byte |
| 18:05 | crazystick | well, I do have the 1-wire master now |
| 18:06 | crazystick | w1_bus_master1/w1_master_slave_count is still zero though |
| 18:06 | jnettlet | do you have any slaves connected? |
| 18:07 | crazystick | i have a ds18b20 - one of the encapsulated ones |
| 18:07 | crazystick | I will see if I need to add some pullup resistor |
| 18:07 | jnettlet | you have the driver enabled in the kernel config? |
| 18:08 | crazystick | yes, wire 30271 2 w1_gpio,w1_therm |
| 18:09 | crazystick | can you have more than one item in the compatible = "w1-gpio"; |
| 18:09 | jnettlet | looks like you need a device-tree node for the sensor as well |
| 18:11 | crazystick | i'm following this: http://webshed.org/wiki/RaspberryPI_DS1820 |
| 18:21 | jnettlet | crazystick, try and change the gpios line to be 1 1 0 |
| 18:26 | crazystick | jnettlet: it just needed a pullup on the data line |
| 18:27 | jnettlet | crazystick, yeah I think the 0 will fix that |
| 18:27 | crazystick | ok. so gpios = <&gpio1 1 1>; --> gpios = <&gpio1 0>; |
| 18:27 | jnettlet | gpio1 1 0 |
| 18:27 | crazystick | oops. ok let me try that |
| 18:31 | jnettlet | crazystick, if you don't mind it looks like 1-wire configuration has been talked about here, http://www.solid-run.com/community/topic1571-20.html . I would appreciate it if you could comment with your success. |
| 18:33 | crazystick | will definitely do that. and if you come up with a good way to add it to wiringX, that will be cool. I added SPI for Hummingboard to WiringX, I think we're just waiting for curlymo to test on some other devices |
| 18:33 | jnettlet | crazystick, yes I appreciate it. I am going to merge those kernel patches as soon as I finish my rebase work |
| 18:35 | crazystick | I still needed the pullup resistor with that change to the dtsi |
| 18:35 | jnettlet | hmmmm we must need to change the mux then. |
| 18:46 | jnettlet | crazystick, what if you just leave the pin in its default state. MX6QDL_PAD_GPIO_1__GPIO1_IO01 0x80000000 ? |
| 18:52 | crazystick | jnettlet: nope, still the same |
| 18:53 | jnettlet | crazystick, okay I will check with the guys using the 3.0.xx kernel and see if they added a pullup and didn't tell me |
| 18:53 | jnettlet | are you using a 10k resistor? |
| 18:54 | crazystick | 4.7k |