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

01:36 pepedog Vodkaaaaaaaaa
10:20 xraxor at this time of the day?
11:13 rabeeh xraxor: ?
11:14 rabeeh ho; pepedog Vodka :)
11:37 _505 rabeeh, is the old wiki locked? Can't log in there to edit pages
11:37 _505 might be good to add a warning that the info over there is for the old cubox
11:44 rabeeh _505: i agree
11:44 rabeeh there is a big confusion about this
11:46 xraxor rabeeh:
11:57 patrickg rabeeh: is there anything I can help you with regarding coreboot?
11:57 rabeeh hi patrickg
11:58 rabeeh i wonder if mrnuke can support the imx6 port for coreboot
11:58 rabeeh or if you have someone else in mind
11:59 rabeeh there are lots of imx6 platforms around and i'm pretty sure coreboot support will be an interesting item
12:00 durandle I have a question regarding flashing the SPI on a CuBox v1, being that it says it has, but wont boot unless I do so via a xmodem transfer of the uboot.
12:00 patrickg rabeeh: it's interesting for sure. as for mrnuke, I think he's up to it. but you'd have to ask him yourself regarding time and interest
12:04 durandle thats better... no more web-irc
12:07 durandle using the installer doesn't work, it gives an error about "/dev/mtd0 (SPI flash) is invalid"
12:07 durandle there are a few forum threads on this issue, none have an actual solution, most seem to end up way off topic.
12:09 rabeeh durandle: how old is your cubox?
12:09 durandle rabeeh: its from the 2nd or third batch of v1
12:09 rabeeh is this with the new plastic or the really old plastic? (i know it's v1)
12:10 rabeeh i.e. plastic with SolidRun logo on top?
12:10 durandle No logo
12:10 durandle so old I guess :)
12:13 durandle rabeeh: have I gone and used a u-boot thats too new for the old model?
12:14 durandle "u-boot-cubox_hynix_cubox_1GB_uart.bin 06-Aug-2013 16:43"
12:14 rabeeh no; it's unrelated to this
12:15 rabeeh it's simply the Linux kernel that loads with the cubox installer doesn't identify the oldie oldie SPI flash on the board.
12:15 rabeeh i can send you a kernel if you want to try out?
12:15 durandle That would be very welcome :)
12:16 rabeeh it's a uImage that you would have to overwrite the older uImage with
12:16 rabeeh now; i have that somewhere
12:16 durandle At some point I plan on getting one of the shiny new models... but as usual, finding the excuse to spend money isn't so easy :)
12:19 durandle rabeeh: How about though when I use bubt and a tfpt server to do it?
12:21 rabeeh durandle: bubt works too
12:22 rabeeh i can't the kernel around; i have built it with the initramfs for the cubox installer
12:24 durandle sorry, not sure what you mean :)
12:26 durandle rabeeh: however, I have used the bubt with tftp to do the flash, which says "Done" all round, but still the box boots with a dim light. Or does bubt on the latest u-boot also have issues accessing the flash?
12:27 durandle all I can get out of putty is "Bootstrap 2.33>"
12:39 rabeeh Bootstrap 2.33 means you have also killed u-boot on the spi flash
12:39 rabeeh you need to recover via xmodem
12:39 rabeeh for xmodem use the _uart version and for bubt use the _spi version
12:40 durandle Ok will try that right now :)
12:45 durandle rabeeh: excellent, at least it boots again ;) thank you so much
12:46 durandle rabeeh: If the patched kernel is an issue, don't worry about it. I can work around it and in a few months I may just get one of the newer ones.
12:50 durandle I just wish there was a reset-button on this thing!
15:27 iio7 Where can I locate information about what exactly the "push-button" does on the pro version of cubox?
15:34 iio7 If nowhere, what exactly does it do?
15:41 MikeSeth there are no buttons on cuboxes
15:41 iio7 yes there are
15:41 MikeSeth whatever you think is a button, isn't
15:42 iio7 you're wrong
15:42 MikeSeth point on a picture?
15:42 iio7 http://www.solid-run.com/mw/index.php/Unbricking_CuBox
15:42 iio7 search for "push-button"
15:42 MikeSeth oh, you mean the *old* cubox
15:42 iio7 it's just above the hdmi on both boxes
15:43 iio7 no I got the pro box, there is one there too
15:43 MikeSeth I dont think they even make those anymore
15:43 MikeSeth according to the page it's a boot mode selection button
15:44 iio7 I just got a brand new yesterday, a CuBox-i4Pro and it has the push-button too
15:44 MikeSeth errr
15:45 iio7 I could not find any info on the push-button for the new box, only something for the old
15:46 MikeSeth the connector mount is standard, it may be unconnected on new cuboxes
15:46 MikeSeth i didnt even realize it was there
15:46 MikeSeth actually on my model I don't think it is
15:46 iio7 it's almost impossible to notice
15:47 iio7 it's very tiny
15:47 MikeSeth as far as I know there isn't a support for anything like this in the bootloader and gpio isn't connected anywhere in any case
16:06 _rmk_ iio7's right... there is a button just above the HDMI
16:56 jnettlet oh that button....don't even push that button!
16:56 Coolgeek the cubox will explode !
16:57 _rmk_ because black buttons surrounded by a black background with black writing should never be pressed?
16:57 Coolgeek only red button can be pushed
17:00 iio7 How can I force the boot process to show on hdmi? I have made a boot.txt -> boot.scr with the following: http://paste.debian.net/76178/
17:00 iio7 But when I boot I still get "No signal" on my monitor.
17:02 _rmk_ I believe the cubox-i uboot supports displaying via HDMI but *not* the Dove based cubox.
17:02 iio7 I have the cubox-i pro
17:03 _rmk_ if what you pasted is for the cubox-i, then why does it talk about dove?
17:04 _rmk_ if you are indeed talking about the imx6 based cubox-i, then its quite probable that the reason you're getting "no signal" is because of a three month old bug that has been low priority for the small number of people to fix... uboot sets the mode slightly slow, and some devices don't recognise the signal.
17:04 iio7 I have no idea. The confirmation from the webshop says pro. Also I can see the boot process fine using hdmi if I boot using the installer.
17:05 jnettlet there is a Cubox Pro as well which is different than a Cubox-i i4Pro
17:05 jnettlet The Cubox Pro is the dove board but with 2GB's of DDR
17:05 iio7 Is there a way to determine which box it is then?
17:06 _rmk_ I have no idea.
17:07 jnettlet if you can get a linux console/terminal, then cat /proc/cpuinfo
17:07 iio7 ARMv7 Processor rev 5 (v7l)
17:07 _rmk_ keep going
17:07 iio7 http://paste.debian.net/76180/
17:07 _rmk_ you'll eventually get to something which says "Hardware:"
17:08 jnettlet That is a dove board
17:08 jnettlet iwmmxt
17:08 _rmk_ right, so that isn't the cubox-i
17:08 _rmk_ It's the older Dove-based cubox
17:08 iio7 I just payed 115$ for that!! I could have gotten the i4-pro!
17:09 _rmk_ and who did you purchase it from? ebay?
17:09 iio7 No New IT
17:10 _rmk_ right, and I'm looking at their site, and NOWHERE does it say that they sell a cubox-i
17:11 _rmk_ They sell a Cubox Pro for ?110 and a Cubox for ?90. Both are the older Dove based ones.
17:11 _rmk_ "800 MHz dual issue ARM PJ4 processor, VFPv3, wmmx SIMD and 512KB L2 cache."
17:11 _rmk_ iio7: PLONK.
17:11 iio7 I got it through amazon, I guess I thought the pro was the new pro.
17:11 iio7 Because of the 2gb
17:12 _rmk_ you mean this: http://www.amazon.co.uk/CuBox-Pro-from-New-IT/dp/B00BXIZASK/ref=sr_1_1?ie=UTF8&qid=1389715932&sr=8-1&keywords=cubox
17:12 _rmk_ "800 MHz dual issue ARM PJ4 processor"
17:12 _rmk_ that also says to me "Dove"
17:13 jnettlet yep
17:14 jnettlet actually rabeeh you may know. What operations can the Armada series dual-issue. I have yet to read documentation that explains it in detail.
17:15 rabeeh i don't recall the exact
17:15 jnettlet iio7, well Amazon has a great return policy. I would start there if you would rather have the i4pro
17:15 rabeeh but the basic arithmetic can dual issue
17:15 iio7 yes, i'll return it!
17:17 _rmk_ I wonder what else iio7 will buy without properly reading the specs
17:17 rabeeh _rmk_: full sd instead of micro sd
17:17 rabeeh 24v / 10A power adapter
17:18 rabeeh reversed where the + is in the inner connection
17:18 rabeeh hehe. and a vga monitor :)
17:19 _rmk_ yes :)
17:21 jnettlet rabeeh, we can probably change the SPL's boot device detection to default to SD1 instead of device unknown. Since all the HB/Cubox-i devices boot from SDHC
17:21 _rmk_ I really ought to get rid of my old 14" crt which doesn't get any use
17:22 _rmk_ maybe iio7 could use it :)
17:22 jnettlet as soon as you get rid of it you know you will need it for testing.
18:11 MikeSeth uhhh, brcmfmac misses 2/3 of scan results, including my ap
18:12 MikeSeth this is probably the gain table issue again argh
20:57 iio7 I have dd from the sd card onto two different USB harddrives. One harddrive is booting and working perfectly, but when I try the other drive I get: http://paste.debian.net/76237/
20:58 iio7 I have mounted the drive from another linux box and it has the same boot.scr as the drive that works. Also if I boot from sd and attach the usb drive, I can mount it and see the files etc.
20:59 iio7 It is cubox pro. Can it be that the cubox pro wont boot some specific harddrives?
21:14 iio7 What does "Bad partition 1" mean?
21:27 iio7 No matter what I choose I get "Bad partition 1"
21:30 iio7 Using "usb info" I get the device. "Mass Storage, USB Revision 2.10 Seagate Portable 2GH76SD2"
21:32 iio7 "usb part" also shows the partition table.
21:32 iio7 Why then do I get "Bad partition 1" when trying to boot from it?
21:38 iio7 Hmm.. I manually got it to boot now.
21:38 iio7 Must be something wrong with the boot.scr file.
23:07 cardiel at which temperature will cubox-i4 become unresponsive?
23:17 cardiel someone got the android image working?