| 09:04 | vpeter | jnettlet: if someone wrote that he has 'Cubox-i4 Pro rev 1.2' - which som is inside? |
| 09:34 | jnettlet | vpeter, that is the the som with with the broadcom wireless |
| 09:49 | vpeter | Yes, as I expected. But seems u-boot is loading imx6q-cubox-i-som-v15.dtb for it. At least what user is saying. |
| 09:59 | jnettlet | vpeter, hmmm it is possible that they have the old BCM4329 chip maybe? Perhaps that is not behaving the same as the 4330 regarding pulling down the GPIOs we use for detection |
| 09:59 | jnettlet | I had definitely tested it, but not specifically inside a Cubox |
| 09:59 | vpeter | How can he see identify this? |
| 10:18 | jnettlet | vpeter, you would need to break boot into the u-boot shell and then check the gpio values by hand. |
| 10:19 | vpeter | Will check this first myself and then ask user to do the same. And compare the result. |
| 11:02 | seb_ | Hi |
| 12:52 | seb_ | Hi |
| 12:52 | seb_ | what type of usb cables I need to make the special cable to fuses the hummingboard pro please ? |
| 13:09 | seb_ | can I use this cable to make the efuses ? |
| 13:09 | seb_ | http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_USBNMC.pdf |
| 13:09 | seb_ | Hi malte_ |
| 13:10 | Artox | seb_: I used a standard usb extension cord with two male plugs |
| 13:10 | Artox | there is no need for any ftdi circuitry |
| 13:12 | Artox | ofc you got to cut it in halves and add the recommended resistor |
| 13:13 | seb_ | HI Artox |
| 13:13 | seb_ | Artox: that usb data cable or just standard low price cable ? |
| 13:15 | seb_ | Artox: 2 usb extension cables then ? |
| 13:15 | Artox | isn't any low-price usb cable a data cable? |
| 13:15 | Artox | either yes, a regualr extension cable |
| 13:16 | seb_ | Artox: thank you :) I will do this |
| 13:19 | seb_ | Artox: have a good day |
| 13:23 | topi` | I don't understand how can I load up initrd from UBOOT cmdline? I can load and boot zImage via "bootz 0x10800000 ..." when I've first loaded the zImage to ram, but it rejects any initrd I try to load |
| 13:23 | topi` | (initrd is the second parameter to bootz) |
| 13:25 | vpeter | Same as zImage but on different location? |
| 13:26 | Artox | topi`: |
| 13:26 | Artox | surely ubtoo has a complaint |
| 13:26 | Artox | something like raw image not supported? |
| 13:30 | topi` | yeah, it did not support the initrd format |
| 13:31 | topi` | which I do not understand, since if I let UBOOT boot automatically, it will actually use that initrd I provided |
| 13:31 | topi` | initrd is a symlink to my.initrd |
| 13:31 | Artox | uhm |
| 13:31 | Artox | you know you cna pass a size argument along |
| 13:31 | Artox | if the initrd is not mkimage'd, the size argumetn is mandatory |
| 13:31 | topi` | ah, then probably it is not mkimage'd |
| 13:31 | Artox | 0xINITRD:0xSIZE |
| 13:31 | topi` | I think it is not, since I just used cpio to create it |
| 13:31 | Artox | where size comes from |
| 13:32 | Artox | ${filesize} directly after ext4load |
| 13:32 | topi` | what kind of headers does mkimage provide? |
| 13:32 | Artox | I load the initrd last, and then pass ${ramdiskaddr}:0x${filesize} to bootz |
| 13:33 | Artox | afaik mkimage provides a checksum, type field, size |
| 13:33 | topi` | OK |
| 14:30 | vpeter | Is it required to have suspend enabled in kernel for imx6? If resume is not possible. |
| 19:51 | mhilt | jnettlet -- I managed to get the parallel ov5640 working, though I do not know what change fixed the issue at this point |
| 19:53 | mhilt | I had removed the subdev module from the build, renamed all ov5640_int references to just ov5640, and changed the entry in the device tree to ov564x instead of ov5640, as I noticed Freescale has in their tree's |