IRC log of #cubox of Wed 14 Jan 2015. All times are in CET < Back to index

00:53 _dab_ what do I need to do to the kernel to see temperature in /sys on an i4pro
00:54 cbxbiker61 cat /sys/devices/virtual/thermal/thermal_zone0/temp
00:54 cbxbiker61 divide by 100
00:57 _dab_ I am using your .config for 3.18.2 and I don't see that file. I presume their is a kernel option to switch it on
00:59 cbxbiker61 cat /sys/class/thermal/thermal_zone0/temp
01:00 _dab_ the termal directory is empty
01:00 _dab_ thermal
01:01 cbxbiker61 config_imx_thermal should be yes
01:02 cbxbiker61 sorry, that was a 3.14 box
01:03 cbxbiker61 but yeah the 3.18 has config_imx_thermal also, so it should work
01:05 cbxbiker61 run the sensors command and see what that says
01:06 _dab_ i have config_imx_thermal = y , sensors says I don't have the the kernel drivers and sensors-detect finds nothing
01:13 mk01 _dab_ : fsl,imx6q-tempmon at dtb is present ??
01:13 _dab_ looking
01:16 _dab_ yep, line 624 of imx6qdl.dtsi
01:23 _dab_ but not in /proc/device-tree
01:34 _dab_ and dtc says tempmon is in the dtb
01:34 mk01 and under /sys ?
01:36 mk01 . /proc shoukd be just 1:1 copy of dtb file
01:37 mk01 but sys is something used further by others
01:37 mk01 if imx_thermal driver succesfully probes the device from dtb
01:38 mk01 it should be accessible via
01:38 mk01 . /sys/bus/platform/drivers/imx_thermal/tempmon.11
01:38 mk01 (at least considering 3.14 structure)
01:41 mk01 and even if driver has not probed it
01:41 mk01 you should see it
01:41 mk01 somwhere under aips bus
01:41 mk01 like
01:41 mk01 ... /sys/devices/soc0/soc.1/2000000.aips-bus/tempmon.11
01:48 _dab_ /sys/bus/platform/drivers/imx_thermal/ has bind uevent and unbind only
01:50 mk01 so driver is active, but device is not bond with it
01:50 _dab_ that would seem to be the case
01:51 mk01 have you found the bus / sensor ?
01:51 mk01 if you do, you can bind (try to) manualy
01:51 mk01 by writing it's identifier to "bind" file under driver
01:51 _dab_ more explanation please
01:52 mk01 but first you have to see t
01:52 mk01 it
01:52 mk01 somewhere
01:53 mk01 (I mean the tempmon sensor)
01:56 _dab_ yes, I will look.
05:26 jason0_ Howdy all, just got a cubox i4 and trying to flash the ignition and or openelec image but getting the error no /boot.scr found then black screen.
08:24 _dab_ on debian jessie 3.18.2 my i4pro is really clunky (slow) with ssh. Anyone had this experience?
11:44 curlymo @all, can someone explain to me once more why we use 0x400130b1 here: https://github.com/linux4kix/linux-linaro-stable-mx6/blob/linux-linaro-lsk-v3.14-mx6/arch/arm/boot/dts/imx6qdl-hummingboard.dtsi#L187
11:46 cbxbiker61 isn't that the address of the muxer?
11:47 curlymo no, that are these: https://github.com/linux4kix/linux-linaro-stable-mx6/blob/linux-linaro-lsk-v3.14-mx6/arch/arm/boot/dts/imx6q-pinfunc.h#L659
11:48 curlymo but looking at the SoC datasheet, i can figure how the different function are build up to that hex
11:48 curlymo can't
11:49 cbxbiker61 i'd like to get a pwm signal out
11:50 curlymo pwm shouldn't be that difficult looking at the datasheet
11:50 cbxbiker61 there are a few pwm signals, just need to figure out how to get them muxed to a pin
11:51 curlymo https://github.com/linux4kix/linux-linaro-stable-mx6/blob/linux-linaro-lsk-v3.14-mx6/arch/arm/boot/dts/imx6q-pinfunc.h#L658
11:51 curlymo check the wiringX source for the hummingboard
11:51 cbxbiker61 beaglebone black is using overlay dts', that sounds like it would useful
11:51 curlymo I set the pin to 0x5 = GPIO, 0x4 = PWM
11:51 curlymo that's all, then you can use the PWM registers
11:52 curlymo https://github.com/pilight/wiringX/blob/master/hummingboard.c#L111
12:37 jnettlet cbxbiker, curlymo rabeeh has posted the MUX settings for pwm in the forums
12:39 cbxbiker61 great i'll have a look
12:40 cbxbiker61 curlymo, wiringX looks good
12:41 cbxbiker61 one thing to do, i need to configure the dts file so i can get the kernel mode pps driver working
12:48 curlymo @jnettlet, maybe you can help me out
13:31 sopparus hello
13:32 sopparus im using cubox with openelec, my 2014 sony tv goes into standby and eventually shut itself down after a while
13:32 sopparus when playing a movie
13:32 sopparus works fine with windows
13:32 sopparus i dont know why though
13:32 sopparus if there is hdmi keep alive or anything
13:33 sopparus could ofcourse be a bug with tv too
13:33 sopparus probably is
13:43 Dom__ rabeeh: i have one more questions about your uvc cam with android. Do you have plugged in the camera and used a camera app, which detects the camera automatically? Do you have configured something?
16:55 moncky Hi All, I have just booted up the ignition simple installer, however my network for reasons beyond my control doesn't have a dhcp server
16:55 moncky is there any way to statically assign an ip address?
17:17 curlymo @jnettlet, are you here?
20:09 curlymo did someone already figured how to control to GPIO muxed special pins like MOSI or TX/RX
20:16 Artox curlymo: maybe this helps? http://www.solid-run.com/community/topic1571.html?hilit=gpio#p11957
20:16 Artox or did you already read it
20:16 jnettlet curlymo, I am back online
20:16 jnettlet what's up?
20:18 curlymo what i said :)
20:18 curlymo i have no clue how to use a let's say muxed MOSI pin as GPIO
20:19 curlymo (memory mapped ofc)
20:21 jnettlet if it is muxed as a GPIO then it should work exactly as any other GPIO
20:22 curlymo we should assume
20:22 jnettlet my guess is that is not the case if you are asking questions
20:23 curlymo normal "GPIO" values are readeable and writeable by using the GPIOX_DR
20:24 curlymo but as far as i read, the "special" pins don't have a GPIOX_DR representation
20:25 jnettlet are you trying to use pin 19?
20:26 curlymo the number would have been step 3 :)
20:26 curlymo for now i'm just trying to memory map everything
20:30 jnettlet curlymo, are you remuxing the pins via device-tree?
20:30 curlymo https://github.com/pilight/wiringX/blob/master/hummingboard.c#L111-L112
20:31 curlymo The address of MOSI = 0x26C and 0x63C
20:31 curlymo so that's not the issue
20:31 curlymo however, what address do we use here: https://github.com/pilight/wiringX/blob/master/hummingboard.c#L114-L117
20:35 curlymo (ps. chapter 28.5)
20:36 curlymo GPIO Memory Map/Register Definition
20:38 jnettlet curlymo, did you read the link that malte posted. I believe you are missing the SION bit for FUNC_GPIO
20:38 jnettlet try changing that from 0x5 to 0x15
20:39 curlymo What chapter?
20:42 curlymo i see 36.3.2
20:43 jnettlet curlymo, yes
20:43 jnettlet sorry hotel wifi is slow and I didn't have the manual local
20:43 curlymo it that's true, where does it say what bit of what register contains the value of e.g. MOSI?
20:43 curlymo MOSI muxed as GPIO i mean ofc
20:44 jnettlet you mean where to read the value from?
20:44 curlymo or set the value
20:44 curlymo line 114 till 117 in wiringX
20:52 jnettlet once it is muxed as a GPIO it should work like any other GPIO. I believe you weren't getting any data back because you were missing the SION bit so you couldn't read from the pin in GPIO mode
20:55 curlymo all that is already clear
20:55 curlymo my question remains
20:55 curlymo please check this link: https://github.com/pilight/wiringX/blob/master/hummingboard.c#L114-L117
20:55 curlymo then look at this: https://github.com/pilight/wiringX/blob/master/hummingboard.c#L53-L58
20:56 curlymo each GPIO in a GPIOX_REG register
20:56 curlymo but i can't seem to find where MOSI is defined
20:57 curlymo GPIOX_REG = GPIO2_DR, that's how they are called
20:59 jnettlet oh sorry I didn't understand what you were looking for.
21:00 curlymo there are 7 32bit registers
21:00 curlymo if i brute force them all (except 0xa8000) nothing happens
21:02 curlymo ( *((unsigned long *)(gpio + 0xa4000 + 4)) = 2147483647; )
21:02 curlymo if i do that with e.g. 0xa4000 GPIO 0, 1, 2, 3, and 7 start working
21:02 curlymo as it should be
21:07 curlymo so, what am i missing :)
21:20 curlymo Is this a clear: "[20:22] my guess is that is not the case if you are asking questions"
21:20 curlymo hard question?
21:22 tvideovi hi jnettlet I understand you have a wheezy distro that supports vpu acceleration, is it possible to try it? thanks
21:27 jnettlet curlymo, I just keep getting distracted. sorry.
21:29 curlymo than focus :)
21:33 Artox tvideovi: maybe you mean the one I got
21:33 Artox there is a repository with teh required vpu packages
21:34 Artox aka libvpu, libfsvpuwrap, gpu-viv.bin, ...
21:34 Artox and 1 experimental image with at least 1 showstopper bug
21:35 tvideovi perhaps, I was informed on the board that I should contact jnettlet but of course I am thrilled to work with anyone on the board, can I contact you to discuss or in direct messaging option on the board?
21:35 Artox "the board"?
21:35 tvideovi the community board
21:35 Artox forum?
21:35 tvideovi but any method you like is good
21:36 tvideovi solid-run/community
21:36 Artox I am afraid I am exactly the oen you?ve been in touch with already
21:36 Catwich I keep masquerading
21:36 Catwich but if you ask me, I prefer IRC most of the time
21:36 tvideovi lol...hiding from jilted lovers??
21:37 curlymo @Catwich, can you remove my account from the opensuse server site
21:37 Catwich OBS? yes
21:37 Catwich sure
21:37 Catwich so, remove; not confirm?
21:38 Catwich arrgh you got 2
21:38 curlymo yep
21:38 curlymo remove
21:38 curlymo we got our own VPS now
21:38 tvideovi thanks Catwich...as you know I have tried and failed to get it working but not sure why...did you see anything in what I sent you
21:38 Catwich well, I saw that the vivante driver was not used
21:38 Catwich xorg took the standard fbdev one instead
21:38 tvideovi btw I have contacted BoundryDevices, they claim to have it working and have an img on their site
21:39 Catwich yep, tehre is a ubuntu 10.10 img or so
21:40 tvideovi yes in my case I never saw the connection to the vivante driver but thought I followed instructions properly but may have messed up
21:40 tvideovi do you know if the BD img actually works as they claim?
21:40 Catwich oh wait
21:40 Catwich your last message said sth on failure to install chromium
21:40 Catwich right?
21:41 tvideovi yes but I was able to rebuild from files on previous attempt in a saved img
21:41 tvideovi what you saw was on your chromium 37
21:41 Catwich well
21:41 Catwich there is only chromium 37 right now
21:41 Catwich its the debian release
21:42 tvideovi that is fine and I used the one from the apt-get from your site but it was clear it did not see any vivante drivers so not sure what I did wrong
21:46 jnettlet curlymo, I will need to get back to you. I don't have a local kernel repo right now and going through the source over the hotel wifi is too slow.
21:47 jnettlet I will start a clone and then look at it in the morning
21:47 curlymo you at least now know what the core of my question is?
21:49 tvideovi the BD distro I looked at is 20141215-nitrogen-3.10.17_1.0.2_ga-trusty-en_US-console_armh and they claim it runs vpu acceleration on their hardware - I can send it to you if you like
21:51 Catwich no need, I am not near my testing grounds
21:52 Catwich I am currently, as mentioned earlier, working on a tiny proof-of-concept image with just vpu-accelerated chromium
21:52 Catwich but its not ready yet for you to try, sadly
21:58 tvideovi thanks Catwich, that is exactly what I am looking for, is there anything I can do to assist?
21:59 Catwich I was near to stating "stay in the channel for a start" :)
22:00 tvideovi lol yes
22:00 Catwich you could download the current image and tell me if it boots
22:00 Catwich but I need to war nyou: the broken part is: there is no known root password
22:00 Catwich and its completely untested
22:00 Catwich in theory it should boot into xdm
22:00 Catwich show a login screen
22:00 Catwich and a default user will log in into chromium
22:01 tvideovi sure, apt-get from you site? name?
22:01 Catwich https://vps.jm0.eu/mxchrome.raw.xz
22:01 Catwich for an sdcard >= 1GB
22:02 Catwich user:password
22:02 tvideovi ok will do back to you in a few minutes
22:02 Catwich imx:linux
22:02 Catwich be aware that it probably isnt working
22:02 Catwich there is a good chance of that
22:03 tvideovi that is fine, will try with serial terminal to see what it says
22:05 cbxbiker61 after watching a video on youtube i realized we should just buy udoo mipi cameras with the ov5640 rather than the rpi version
22:10 tvideovi malte - I sent you the link via private message as I could not do it on irc
22:18 tvideovi Catwich - started to boot and then hung up after 'Booting from net.... - do you want the complete console log?
22:21 Catwich hmmmmm
22:21 Catwich well, I dont think I need the log
22:21 Catwich it means I need to check tomorrow evening
22:23 tvideovi when I used ctl c i got an Abort and then Booting uImage, Wrong Image Format for bootm command, ERROR: can't get kernel image!
22:28 Catwich well
22:28 Catwich because there is no uImage
22:28 Catwich I probably just messed the uEnv.txt up
22:28 Catwich you can try copying the one from igors image
22:28 Catwich if you like
22:29 malte thanks @tvideovi
22:32 tvideovi OK will try but right now having hard time to read card on different computer - burning a new img on different sd card
22:42 tvideovi Catwich - new card but same result
22:44 Catwich well, be patient
22:44 Catwich I hope to get a working one up over the weekend