00:05 | `jpi | i would like to help out |
00:05 | `jpi | do you have your code available somewhere ? |
00:20 | punkt | `jpi: yes, wait i will prepare a branch |
00:26 | punkt | `jpi: git://git.pengutronix.de/git/mgr/barebox.git cubox |
00:27 | punkt | `jpi: http will also work, i think |
00:28 | punkt | `jpi: http://git.pengutronix.de/?p=mgr/barebox.git;a=shortlog;h=refs/heads/cubox |
00:29 | punkt | `jpi: initial lowlevel support is away from ready, but at least has a structure, common to other bootheaders... |
00:30 | punkt | `jpi: we will need a defconfig, as the NS16550 serial driver will need to be enabled for that machine |
00:31 | punkt | `jpi: with that stack, its already possible to load that image into ram, and jump into the image with go from u-boot |
00:32 | punkt | its getting late here, will better jump into bed now ;) good night |
01:58 | `jpi | ok thanks |
01:58 | `jpi | me too going to bed |
12:47 | RandomPixels | hello |
13:00 | rabeeh | hi RandomPixels |
13:19 | RandomPixels | have you tested the ubuntu 12.10 on the cubox? does it work better than the 10.04 ? |
13:20 | RandomPixels | the 10.04 had problems with audio and not enough memory for opening apps (like vlc) |
14:05 | numpty | hello |
14:05 | numpty | is there anyone around to give a hand? |
14:05 | Guest6710 | Hello, is there anyone around to give a hand? |
14:06 | Coolgeek | don't ask to ask, just ask |
14:06 | Guest6710 | :) |
14:06 | Guest6710 | ok I'm on centOS at work |
14:06 | Guest6710 | can't get a serial connection to cubox |
14:07 | Guest6710 | anyone know how I can route out what device it is, because it's not ttyUSB0 |
14:07 | Guest6710 | I only have access to screen, not putty as well |
14:08 | Guest6710 | dmesg | grep tty |
14:08 | Guest6710 | returns me |
14:08 | Guest6710 | console [tty0] enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A |
14:09 | Coolgeek | /dev/ttyS0 |
14:09 | Guest6710 | so |
14:09 | Guest6710 | sudo screen /dev/ttyS0 8250 |
14:10 | Coolgeek | you have to tell screen the speed |
14:10 | Guest6710 | ok cool this is where I'm probably falling down |
14:10 | Guest6710 | dmesg | grep ttyS0 |
14:10 | Guest6710 | returns |
14:10 | Guest6710 | serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A |
14:10 | Guest6710 | 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A |
14:11 | Guest6710 | is the speed 8250? |
14:15 | Guest6710 | screen just crashes on me |
14:15 | Guest6710 | I do this wich cubox unplugged from the power right? |
14:15 | Guest6710 | that's how I've done it before |
14:15 | Guest6710 | then had to plug the power in to boot it up and monitor the output |
14:19 | Guest6710 | I'm getting nothing |
14:22 | Guest6710 | any ideas? |
14:23 | Guest6710 | I'm just going for lunch but I could really do with getting debian up and running on this thing, It's been out of use for months now and I'm a bit stuck |
14:44 | Coolgeek | Guest6710: http://www.solid-run.com/mw/index.php/Cubox_serial_port |
15:20 | Guest6710 | what is the cubox v2? |
15:20 | Guest6710 | is it the cubox pro? |
15:22 | rabeeh | cubox v2 is a newer version of cubox with some board level modifications |
15:22 | Guest6710 | Hey rabeeh |
15:22 | rabeeh | for instance a prolific usb to serial was used inside v1, but in v2 ftdi usb to serial is being used |
15:22 | Guest6710 | I don't think I'll have that version then |
15:22 | rabeeh | hi |
15:22 | Guest6710 | mines about a year old |
15:22 | Guest6710 | ish |
15:22 | rabeeh | if the micro-usb connector is beneath the esata then it's v2 |
15:23 | rabeeh | it's probably a v1 then |
15:23 | Guest6710 | ohhh |
15:23 | Guest6710 | no it is beneith the esata |
15:23 | Guest6710 | that would make sense why I can't connect on osx |
15:23 | Guest6710 | I'd installed the wrong driver |
15:23 | rabeeh | main difference between v1 and v2 is the usb to serial |
15:23 | rabeeh | right. you should be getting the prolific one |
15:24 | Guest6710 | ok but on centos: |
15:24 | Guest6710 | dmesg | grep tty |
15:24 | dmitrijus | rabeeh: btw, why the switch to ftdi? :) |
15:24 | Guest6710 | console [tty0] enabled |
15:24 | Guest6710 | serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A |
15:24 | Guest6710 | 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A |
15:25 | Guest6710 | how can I connect to serial using screen with that info? |
15:25 | Guest6710 | I'm missing something somewhere |
15:27 | rabeeh | the switch to ftdi is because it's smaller, so we were able to shove in the bottom board :) |
15:27 | rabeeh | the prolific chip is 4-5 times bigger |
15:31 | Guest6710 | I can't connect using "screen /dev/ttyS0 115200" |
15:31 | Guest6710 | or other things I've tried (blindly) |
15:31 | punkt | rabeeh: btw. why does the xmodem protocol fail so often, when trying to xfer a new bootloader |
15:32 | rabeeh | it doesn't fail for us |
15:33 | rabeeh | which cable are you using? |
15:33 | rabeeh | i think i'v noticed once that a really really cheap slim cables don't do the work really good |
15:33 | Guest6710 | me? or punkt? |
15:33 | rabeeh | but typically with the xmodem you should be getting a nack then frame would be retransmitted |
15:33 | rabeeh | punkt |
15:33 | Guest6710 | k |
15:34 | rabeeh | Guest6710: why screen? |
15:34 | Guest6710 | I'm at work and can't install putty |
15:34 | rabeeh | what is the terminal emulation that can be used in Mac? |
15:34 | rabeeh | oh |
15:34 | Guest6710 | on centos here |
15:34 | rabeeh | minicom |
15:34 | rabeeh | ? |
15:34 | Guest6710 | lets try that |
15:34 | rabeeh | minicom -s |
15:34 | Guest6710 | no minicom |
15:35 | Guest6710 | but at home I was on vmware ubuntu |
15:35 | Guest6710 | on mac |
15:35 | rabeeh | what do you want to do? |
15:35 | Guest6710 | but now I know I should be using v2 maybe I can get a connection that way |
15:35 | rabeeh | cubox installer support hdmi |
15:35 | Guest6710 | ok |
15:35 | Guest6710 | so maybe I just need to clarify something |
15:35 | dmitriju | 15:35 * dmitrijus does screen |
15:35 | dmitrijus | Guest6710: /dev/ttyS |
15:35 | dmitrijus | is your serial port :) |
15:36 | Guest6710 | I've used cubox installer to install debian |
15:36 | Guest6710 | and ubuntu in the past |
15:36 | dmitrijus | not the adapters' |
15:36 | Guest6710 | but I can't get access to the box after that |
15:36 | Guest6710 | through ssh |
15:36 | Guest6710 | so that's where I need to connect through serial to set it up yes? |
15:36 | Guest6710 | because that won't have hdmi support to begin with? |
15:36 | Guest6710 | also your installerv2 doesn't have the boot in it apparently that you need to copy over from v1 |
15:37 | dmitrijus | Guest6710: you need something /dev/tty*USB* |
15:37 | Guest6710 | ok nothing is showing up here |
15:37 | Guest6710 | but that makes sense |
15:37 | Guest6710 | thanks |
15:38 | Guest6710 | I'll try with v2 drivers for osx tonight |
15:38 | Guest6710 | but I just need to clarify what I'm expecting |
15:38 | Guest6710 | should I just be able to boot the cubox after debian install with hdmi connected to see a shell output? |
15:38 | Guest6710 | cause I only get connection when I use cubox installer |
15:39 | rabeeh | hmm... i'm not sure if debian gives agetty login on the framebuffer |
15:39 | Guest6710 | I'll probably try ubuntu |
15:39 | Guest6710 | just had enough of archlinux which I had working |
15:39 | Guest6710 | but became a pain |
15:40 | rabeeh | why is that? |
15:40 | rabee | 15:40 * rabeeh likes arch |
15:40 | Guest6710 | well I just don't have the experience or time to keep on top of it |
15:41 | Guest6710 | I installed the new version and now daemon scripts won't work |
15:41 | Guest6710 | I have to swap to something else |
15:41 | Guest6710 | also using forums to debug stuff.. |
15:41 | Guest6710 | everything changes and becomes new |
15:41 | Guest6710 | was just too much hastle for an end user |
15:41 | Guest6710 | for you I'm sure you know what you're doing and love it |
15:42 | Guest6710 | but it took up too much of my time |
15:43 | rabeeh | in short... linux :) |
15:43 | rabeeh | in the installer there is a xubuntu image |
15:43 | rabeeh | the only issue reported that it has is network |
15:44 | rabeeh | (you need to remove some udev rule and reboot) |
15:44 | Guest6710 | but that has gui |
15:44 | Guest6710 | I'm after headless |
15:44 | Guest6710 | I had archlinux running fine until it kicked me out of root |
15:46 | punkt | rabeeh: it was a cheap and slim cable, i will retry with another one... with that cable it was only possible to xfer via cutecom |
16:16 | Guest6710 | gotta go |
16:16 | Guest6710 | I'll try serial on osx using the v2 when I get home |
16:16 | Guest6710 | thanks guys |
17:49 | Cubcat | What the... |
17:50 | Cubcat | I saw on wiki CuBox v1 and CuBox v2 |
17:50 | Cubcat | How to know which CuBox I have ? |
17:52 | Coolgeek | where is the serial port ? |
17:52 | Coolgeek | on the side or at the bottom ? |
17:52 | Coolgeek | right side or back side ? |
17:53 | Cubcat | right side |
17:53 | Cubcat | and side. |
17:53 | Coolgeek | right side => v1 |
17:53 | Cubcat | :( |
17:54 | Cubcat | thanks |
21:04 | ninny | to start up where I left of at lunch |
21:04 | ninny | I still can't get a serial connection |
21:04 | ninny | dmesg | grep ttyUSB |
21:04 | ninny | [ 103.388126] usb 2-2.2: FTDI USB Serial Device converter now attached to ttyUSB0 |
21:04 | ninny | which is good |
21:04 | ninny | only appears when I attach cubox |
21:05 | ninny | putty -serial -sercfg 115200,8,n,1 /dev/ttyUSB0 |
21:05 | ninny | won't connect |
21:05 | ninny | any ideas? |
21:17 | ninny | ok I'm in with minicon |
21:17 | ninny | thank god for that! |
23:00 | ninny | Hey all, I have ubuntu core installed but can't see what the next steps are. I have no internet connection by the look of it, but I can't tell cause I don't have ping. apt-get update isn't working |
23:11 | ninny | anyone? |