| 07:21 | topi` | rabeeh: it seems you are using a PIC16 as the controller of on-board power? it controls the voltages to many subsystems if I'm not mistaken. Is it possible to use this as a Watchdog? |
| 07:22 | topi` | I'm talking about the CF Pro |
| 07:23 | topi` | our client has some weird requirements, they want to be able to see the state of communications from the LEDs and it seems this PIC16 is actually controlling 2 leds. |
| 08:46 | rabeeh | topi`: don't get too excited |
| 08:47 | rabeeh | that PIC is typically not assembled since it was meant to put awake the SoC from power down. |
| 08:47 | rabeeh | the wires are there but we never assembled and tested it; at all |
| 10:06 | cpuid | hello SolidRun is there any plan to release an ARMv8 (64bit) board in 2017? |
| 10:28 | topi` | rabeeh: ok :) so the LEDs are not active? |
| 10:29 | topi` | cpuid: they already have one: the 8048 Community board :) |
| 10:29 | topi` | Marvell 8040 |
| 10:30 | topi` | but I agree, for our intents and purposes it would be best to have 64-bit arm-based systems, since everything else these days is 64-bit or seems to require 64bit |
| 10:31 | topi` | I tried building LevelDB on a 32bit system and ran into a lot of problems, because at some point they did 64-bit optimizations in a way that breaks the build for 32bit users |
| 10:31 | topi` | just to name one example :) |
| 10:37 | cpuid | yeah, same for software developed in go lang, unstable on 32bits |
| 10:58 | jnettlet | cpuid, we have already released one :) Our Marvell 8040 board. |
| 10:58 | jnettlet | but yes there will be additional ARMv8 boards throughout 2017 |
| 11:00 | cpuid | when will it exit the evaluation state and get an enclosure? |
| 11:26 | jnettlet | cpuid, the 8040 board is a traditional mini-itx form factor. |
| 11:27 | jnettlet | we are doing a second small production run beginning of Jan to fix some hardware bugs we found. |
| 11:55 | cpuid | ok |
| 12:26 | topi` | jnettlet: is this why my board hasn't shipped yet? |
| 12:26 | topi` | I can be OK with bugs if it doesn't affect my use case :) |
| 13:21 | jnettlet | topi`, yes that is the delay |
| 13:22 | jnettlet | I haven't even received a board yet |
| 13:27 | jnettlet | and for anyone using the iMX6 boards. New patchsets have been pushed to the kernel repo. |
| 13:56 | cpui | 13:56 * cpuid kicks riddle |
| 17:24 | ngochai_ | Hi guys, I'm trying to create initrd for my hummingboard and load it with uboot, but I'm getting VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 |
| 17:25 | ngochai_ | but right before that it shows: VFS: Mounted root (ext2 file system) on device 1:0 |
| 17:25 | ngochai_ | what's wrong? |
| 19:10 | jnettlet | ngochai_, which image are you using? I think your u-boot build may be missing the option needed to use the initramfs. |
| 19:11 | jnettlet | ngochai_, please refer to this patch.. https://raw.githubusercontent.com/mxOBS/deb-pkg_u-boot-cubox-i/master/debian/patches/u-boot-raw-initrd.patch |
| 19:21 | ngochai_ | jnettlet, thank you for your help, it was my mistake, wrong script interpreter in linuxrc causing it exit and the kernel continues |
| 19:21 | jnettlet | ngochai_, okay great. glad you got it sorted out |
| 21:19 | ngochai_ | jnettlet, what should be set so I can see the kernel msg if I connect to the hummingboard through those GPIO pins using minicom? |
| 21:19 | ngochai_ | right now I only can those msgs if I connect a HDMI cable to a monitor |
| 21:20 | jnettlet | ngochai_, our you need to set the default console to ttymxc0 |
| 21:20 | jnettlet | but all our images do that by default. |
| 21:21 | ngochai_ | what i have is: videoconsole=video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 consoleblank=0 |
| 21:22 | ngochai_ | should it just be videoconsole=console=ttymxc0 |
| 21:22 | ngochai_ | ? |
| 21:28 | ngochai_ | jnettlet, got it, thanks |
| 22:00 | ngochai_ | jnettlet, with console=ttymxc0 how do I setup my keyboard? I don't see what I type in minicom |
| 22:05 | Artox | ngochai_, minicom might be m ad at you |
| 22:05 | Artox | thinking flow control could be enabled |
| 22:06 | Artox | ngochai_, http://tio.github.io/ is easier to use, but probably also much less tested than minicom |
| 22:09 | ngochai_ | both hard and software flow control is off |
| 22:09 | Artox | ngochai_, then idk |
| 22:09 | Artox | iy you type on the serial console |
| 22:09 | Artox | everything should be echoed |
| 22:34 | ngochai_ | I use pin 1 for VCC, 6 for GND, 8 and 10 for TX,RX, is it corrent? |
| 22:35 | ngochai_ | I can see uboot, kermel messages. problem is that whatever I type does not do anything |