**** BEGIN LOGGING AT Sat Jul 27 02:59:58 2013 Jul 27 03:03:38 ka6sox-away: pong Jul 27 03:04:23 jj2baile, how goes the video? Jul 27 03:07:20 Well, have the camera set up and stuff, Figuring out exactly what im going to record. Jul 27 03:07:40 kk Jul 27 03:07:54 I'm going to have limited access this next week... Jul 27 03:08:04 so seeing this before I leave would be helpful Jul 27 03:08:22 Well, I might need to wait till the middle of the night to do the recording now actually. People filtering back into the office. Jul 27 03:08:28 ka6sox-away: When do you leave? Jul 27 03:08:37 Tuesday I'll be on top of Half Dome so I think I'll get enough service there to fill out the eval Jul 27 03:08:49 jj2baile, 11am sunday your time Jul 27 03:09:13 Alright. well Ill be trying to do this today. Considering i've already set stuff up. Jul 27 03:09:15 everything else is in order...but I need the video :) Jul 27 03:09:51 Any general tips/suggestions for the video? Jul 27 03:10:50 hmmm....I carefully avoid doing video...mostly an audio man here :) Jul 27 03:11:57 mluckham, ping? Jul 27 03:12:11 can we get your traces for the code that jj2baile has? Jul 27 04:07:37 jj2baile, add diagrammes and mluckham's traces..and talk about the architecture with the PRU handling RT things. Jul 27 04:13:10 Hm Ok. So more of an informational talk than a demo Jul 27 04:13:12 I like that more. Jul 27 04:13:34 Alright thanks for the guidance. Won't be able to shoot tonight then, would need to get a few other things prepared Jul 27 04:16:04 understood Jul 27 04:16:10 I think thats more where we are now Jul 27 09:43:29 koen: ping.. Jul 27 09:43:40 3.11 rc2 hangs on loading kernel.. Jul 27 09:43:47 no serial messages either.. Jul 27 09:43:50 all leds on Jul 27 09:44:56 ################################################################# Jul 27 09:44:58 ################################################################# Jul 27 09:45:00 ################################################################# Jul 27 09:45:02 ################################################################# Jul 27 09:45:04 ################################################################# Jul 27 09:45:06 ################################################################# Jul 27 09:45:08 ###################### Jul 27 09:45:12 625 KiB/s Jul 27 09:45:12 done Jul 27 09:45:14 Bytes transferred = 3771944 (398e28 hex) Jul 27 09:45:16 link up on port 0, speed 100, full duplex Jul 27 09:45:18 Using cpsw device Jul 27 09:45:20 TFTP from server 192.168.0.1; our IP address is 192.168.0.250 Jul 27 09:45:22 Filename 'dtb'. Jul 27 09:45:24 Load address: 0x815f0000 Jul 27 09:45:26 Loading: #### Jul 27 09:45:28 569.3 KiB/s Jul 27 09:45:30 done Jul 27 09:45:32 Bytes transferred = 20437 (4fd5 hex) Jul 27 09:45:34 ## Booting kernel from Legacy Image at 80200000 ... Jul 27 09:45:36 Image Name: Linux-3.11.0-rc2-00166-g665f96d- Jul 27 09:45:38 Image Type: ARM Linux Kernel Image (uncompressed) Jul 27 09:45:40 Data Size: 3771880 Bytes = 3.6 MiB Jul 27 09:45:42 Load Address: 80008000 Jul 27 09:45:44 Entry Point: 80008000 Jul 27 09:45:46 Verifying Checksum ... OK Jul 27 09:45:48 ## Flattened Device Tree blob at 815f0000 Jul 27 09:45:50 Booting using the fdt blob at 0x815f0000 Jul 27 09:45:52 Loading Kernel Image ... OK Jul 27 09:45:54 OK Jul 27 09:45:56 Using Device Tree in place at 815f0000, end 815f7fd4 Jul 27 09:46:00 Starting kernel ... Jul 27 10:26:18 anybody else using 3.11? Jul 27 13:55:50 _av500_: av500 ping Jul 27 14:07:59 vvu: using 3.11? Jul 27 14:08:06 nop Jul 27 14:08:17 k. cant get it to boot Jul 27 14:08:31 serial argument is right? Jul 27 14:08:46 same setup works for 3.10 Jul 27 14:08:56 koen updated some tags to 3.11 Jul 27 14:09:08 and all leds switch on. and kernel hangs at starting kernel Jul 27 14:09:19 serial argument incorrect wont cause all leds to light up.. Jul 27 19:30:46 koen: ping.. Jul 27 19:30:56 anyone else running the latest 3.11 on the BBB? Jul 27 22:16:06 ds2: ping Jul 27 22:22:11 ZubairLK: got 3.11 to boot? Jul 27 22:22:16 nope Jul 27 22:22:22 not trying btw Jul 27 22:22:30 stuff like this is something the makers know Jul 27 22:22:37 saw the pull request and thought so Jul 27 22:22:39 it'll be something quirky in a corner somewhere Jul 27 22:23:00 a bit 'confident' that it'll work :p Jul 27 22:23:05 3.8 pull request is solid Jul 27 22:23:24 3.11 pull request is without any tests :p Jul 27 22:23:26 its under development anyways.. Jul 27 22:23:40 uoke :) Jul 27 22:23:46 so project going good i see Jul 27 22:24:04 yea. its going good up till now Jul 27 22:24:08 thankfully :) Jul 27 22:24:10 what about you? Jul 27 22:25:18 have some issues with the serial buffer size Jul 27 22:25:29 the default kenrel buffer size is 4096 bytes for a serial port Jul 27 22:25:47 and sending data at that rate is slow for a full Angstrom .img from Android to BBB Jul 27 22:26:01 on the Android part if i send chunks of more bytes Jul 27 22:26:07 it overflows the buffer at some point Jul 27 22:26:12 and kills the connection Jul 27 22:28:11 s/kills/hangs Jul 27 22:30:50 i see Jul 27 22:31:20 any hint how can i make the buffer larger? Jul 27 22:31:20 trying to hack kernel to increase serial speed and buffer size? Jul 27 22:31:24 or it's hardcoded? Jul 27 22:31:37 nothing is hardcoded. Jul 27 22:31:37 searched google but nothing good came up Jul 27 22:32:17 are you sending angstrom img file to uboot? Jul 27 22:32:23 or the linux kernel? Jul 27 22:32:28 angstrom img Jul 27 22:32:31 1.9 gigs Jul 27 22:32:35 to a custom ramdisk Jul 27 22:32:40 with busybox Jul 27 22:32:56 i have serial usb gadget running which emulates a serial port over usb Jul 27 22:33:10 basically it shrinks down to serial read/write Jul 27 22:33:40 emulation isn't limiting is it? Jul 27 22:33:51 don't think so Jul 27 22:34:17 might be worth checking out if there is some hard coded value in ther Jul 27 22:34:37 although. usb is faster than serial. shouldn't choke the link. Jul 27 22:34:55 true but still there is a serial driver that has the buffer size Jul 27 22:35:25 a link with code? Jul 27 22:35:29 to the serial driver Jul 27 22:35:55 kernel serial driver Jul 27 22:35:58 g_serial Jul 27 22:36:09 don't know much about it Jul 27 22:38:59 Jj2baille, I was in Detroit today, met jkridner. Jul 27 22:39:41 Do you have the link to the trace shot still? Jul 27 22:39:52 vvu: you do realize serial max speed is 115200 bits per second. even with 115kbps you'll have a hard time sending 1.9gig.. Jul 27 22:40:41 it's over an usb link, so speed does not matter Jul 27 22:42:59 anyway i did something like tftp send data; wait for ack; send again; wait for ack Jul 27 22:43:15 not to overflow the buffer with 2048 bytes chunks of data Jul 27 22:43:24 and it seems to work okish need to test it more Jul 27 22:43:39 i see Jul 27 22:43:54 if i put it with 512 bytes chunk of data it works really nice but i'll be until 2morrow here sending that .img :)) Jul 27 22:44:19 i'm just randomly googling stuff. know about Zmodem protocol? Jul 27 22:44:45 i need to code zmodem on the android side and need to have a working system until monday mornin when eval starts Jul 27 22:44:49 so not right now :) Jul 27 22:44:53 but thought about that too Jul 27 22:45:16 with my approach i'm at the point of cracking the bug and getting it to work Jul 27 22:45:17 shouldn't be a need to code zmodem. some existing package should be there.. Jul 27 22:45:36 hmm. Jul 27 22:45:49 i'm hoping evaluations will pass smoothly.. Jul 27 22:46:04 greg says just keep working n its all ok. Jul 27 22:46:04 same here. found some zmodem packages but they need root access to the port Jul 27 22:46:19 i need to code zmodem with the USB Host API Jul 27 22:46:26 not plain c then cross-compile Jul 27 22:47:48 i see Jul 27 22:47:53 good luck! Jul 27 22:51:35 time for some zzz Jul 27 22:51:37 gn folks Jul 27 23:48:01 anybody here? Jul 28 01:27:48 mluckham-mobile: https://www.dropbox.com/s/wx91ijgiz8dh1sb/prucap1.jpg <- This, right? Jul 28 01:44:25 Yes, that's right Jul 28 02:47:44 mluckham-mobile: How was the maker faire? **** ENDING LOGGING AT Sun Jul 28 02:59:58 2013