**** BEGIN LOGGING AT Sat Jan 02 02:59:59 2016 Jan 02 03:18:27 zmatt-: there? Jan 02 03:21:32 does the CLKACTIVITY_EMIF_GCLK domain need to be enabled in the CM_PER_L3_CLKSTCTRL register before accessing the emif registers? Jan 02 03:25:01 also, what's the difference between L3 and L3S? Jan 02 03:29:26 zmatt-: help? Jan 02 03:33:10 gosh, where is everyone? Jan 02 03:36:51 Hungover. Jan 02 03:38:28 ha! Jan 02 03:39:41 is there a utility for the bbb under debian that will read and report registers? (e.g., the CM_PER_L3_CLKSTCTRL register) Jan 02 03:44:27 I have no idea. Probably. Jan 02 03:44:37 Or maybe not. Jan 02 03:48:47 bool f; (f == 0) || (f == 1) Jan 02 05:47:20 dead around here man... Jan 02 05:47:47 how about another white russian? Jan 02 12:40:03 i am trying to boot from one of the images providede at http://elinux.org/Beagleboard:BeagleBoneBlack_Debian Jan 02 12:40:19 but it looks as if the bootloader does not accept those Jan 02 12:41:28 my original image on the BBB is a debian with a 3.8 kernel, if i remember right there was some transition with uboot, is it possible that teh uboot on the internal mmc that was deliverd with the board can not boot these sdcard images Jan 02 12:43:46 if i hold the boot button there is no uboot loaded , i know since i am connected to the serial interfece, further there is no fat partition on these images, so i guess they can not hold an uboot at all Jan 02 12:46:51 tat: how did you write them to SD card? Jan 02 12:47:02 dd if= of= bs=10m Jan 02 12:47:31 i used bone-debian-7.9-console-armhf-2015-11-03-2gb.img Jan 02 12:48:22 so you uncompressed the image first? Jan 02 12:49:04 the partition is writen to the sdcard, but i can not start a uboot from that sdcard, and the uboot that is located at the intrnal mmc is not booting that sd card, i had the same problem with my last bbb like a month ago, seems like there has been a transition in bootloader setup at some point Jan 02 12:49:19 tbr: yes i run xz -d first Jan 02 12:49:35 also you must press the S2 button next to the SD card slot before powering up the board Jan 02 12:49:56 what do you see on the serial console if you do that? Jan 02 12:50:00 tbr: did that it just shows a lot of CCCCCCCCCC in the serial terminal Jan 02 12:50:20 C means that it didn't find a boot loader at all Jan 02 12:50:54 did you write the image to the raw device? Jan 02 12:51:07 tbr: yes Jan 02 12:51:22 if of=/dev/sdx1 then that's wrong Jan 02 12:51:29 /dev/rdisk Jan 02 12:51:33 /dev/rdisk1 Jan 02 12:51:53 it is osx, that is the device not the first partition Jan 02 12:52:03 do you see the partition table? Jan 02 12:53:21 https://gist.github.com/morriswinkler/6f79ae2fb48d86db42aa Jan 02 12:53:44 only a ext partition there, starting at 2048 Jan 02 12:55:10 as far as i understand the uboot has been moved into the first 2048 bytes, i had that problem before Jan 02 12:55:41 i installed BBB-eMMC-flasher-v2014-06-2014.11.28.img as intermediate image and than it worked Jan 02 12:56:27 but i would like to figure out what that problem is exactly, i mean there must be a version that is not able to boot from the new images Jan 02 12:56:50 is the size of the first partition 3.5GB? Jan 02 12:57:18 it is 1.6 GB Jan 02 12:57:30 sounds about right Jan 02 12:57:36 /dev/disk1s1 1.6Gi 218Mi 1.3Gi 14% 13156 95708 12% /Volumes/rootfs Jan 02 12:57:43 Filesystem Size Used Avail Capacity iused ifree %iused Mounted on Jan 02 12:58:02 it is a console image, so it uses only a subset of debian packages Jan 02 12:58:39 I don't see any reason why it shouldn't be able to boot Jan 02 12:59:42 i can rewrite the image to make sure there is no io error Jan 02 13:00:15 did you use this card successfully with the BBB before? Jan 02 13:00:45 might be worth trying a different card? also checking that the microSD slot is clean Jan 02 13:01:19 i think not this one, but i have no reason to belive it is the card, i had the exact same problem last time i flashed an other BBB Jan 02 13:02:04 i use OSX to copy the image to the sdcard, this is raw io copy with dd, so i am certain this should not be the problem Jan 02 13:02:28 it shouldn't Jan 02 13:02:39 how are you powering the BBB? Jan 02 13:02:56 as far as i can remember, i used an intermediate image, that would boot and flash, once this image had been flased the bootloader from the newly flashed image could boot a more recent version Jan 02 13:03:07 5V DC powersuply Jan 02 13:03:20 2250 mA Jan 02 13:05:26 i will reflash the current image, and try once more, if that is not working i will try the internediate image from last time, if that works it would have something to do with moving the bootloader from a fat partition into the first bytes of the sdcard Jan 02 13:06:06 it is just i do not really remember how the boot mechanism on the BBB is designed, can you point me to some documentation about that Jan 02 13:09:22 ok found it, so for me the only logical explanation is that the bootloader on the image is missing Jan 02 13:13:01 you could take any other image and rewrite the space before the first partition from it Jan 02 13:13:55 where exactly is the bootloader located Jan 02 13:15:07 if it's not on a partition, then MLO must be at 3 offsets at the beginning of the raw device Jan 02 13:15:14 all three must be identical Jan 02 14:22:03 ok it works if i press the power button ? Jan 02 14:22:46 nope, my mistake Jan 02 16:08:28 U-Boot SPL 2015.10-00001-g51aa16b (Oct 21 2015 - 14:16:21) Jan 02 16:08:29 Card did not respond to voltage select! Jan 02 16:08:29 spl: mmc init failed with error: -17 Jan 02 16:08:30 ### ERROR ### Please RESET the board ### Jan 02 16:08:43 that is how far i get now, with playing arround a bit Jan 02 16:13:20 what a grap Jan 02 16:13:39 if i press the card real hard against the pins it works Jan 02 16:14:13 now i booted the image with the flasher, so i am stuck holding the card until the reflash is done Jan 02 16:19:00 really, how can that be so bad, it only works if i press the sdcard really hard against the pins Jan 02 17:27:44 Howdy, I tried to create a new topic on the forums and thought I fowwlowed the process correctly, but I am unable to find the new topic. Also, how does one list the topics by new entry? Thank you. Jan 02 17:28:10 followed Jan 02 17:29:46 i justed booted kernel 4.1.15 on a BBB , any idea what loads this pin ? pin 66 (44e10908.0): 4a100000.ethernet (GPIO UNCLAIMED) function cpsw_default group cpsw_default Jan 02 17:29:47 pin 66 (44e10908.0): 4a100000.ethernet (GPIO UNCLAIMED) function cpsw_default group cpsw_default Jan 02 17:30:13 i can not remember that this pin was in use before is that an aditional ethernet port ? Jan 02 18:12:30 tat: so from the BBB schematics, this pin is in use, but on the mainline 4.1.15 it seems not to be explicitly assigned in the bbb devicetree, are you using a mainline kernel, or where did you get the kernel from? Jan 02 18:15:46 so per default the pin is configured as mii1_col and in your version of the devicetree its just explicitly configured in MODE0 as mii1_col as well (which does no harm), thats probably the reason why you get the message now, i could be off though Jan 02 18:45:55 zmatt-: dude, you awake? Jan 02 18:47:03 what is the rom boot address that gets vectored to on power up? Jan 02 18:50:22 i've got ccs hooked up to our prototype, and want to run the boot code to load the sdcard image Jan 02 18:51:27 why can't i "Load..." a .elf file in CCS (in a debug context)? Jan 02 18:52:09 it's looking for .out files, etc. Jan 02 18:52:30 is this thing on? Jan 02 18:52:40 Jan 02 19:00:59 damn europeans - they take weeks off for holiday... Jan 02 19:04:41 They have too keep everything running in the mean time. Jan 02 19:05:03 especially the beer dispensers! Jan 02 19:09:44 I wouldn't know really. Likely they do although someone has to operate those as well. Jan 02 19:10:24 They do get things done just not the same as other people. Everyplace is different. Jan 02 19:57:08 Are the forums working today? I have been unable to post a question. I follow the instructions and it looks like it posts, but I cannot find my question anywhere. Jan 02 21:22:48 zmatt-: dude? Jan 02 21:55:45 well, looks like beagle-x15 will be included in the upcoming kernel in debian experimental Jan 02 21:55:56 though i wasn't able to get USB or eSATA to work ... Jan 02 22:09:56 Hmmm no USB? Jan 02 22:10:47 yeah, using mainline kernel ... might be missing a few config options in the kernel build ... Jan 02 22:11:03 or, hopefully it's not incompatible with other options compiled into the debian kernel Jan 02 22:11:42 for a long time, the beaglebone black wouldn't work with the necessary drivers for usb working compiled as modules, they had to be built-in ... Jan 02 22:14:36 best poke rcn-ee Jan 02 22:15:59 yeah, will likely do that at some point Jan 02 22:16:32 but at least microsd, emmc, ethernet, framebuffer all will work out of the box for starters Jan 02 22:22:48 tis a fair start Jan 02 22:23:05 since most arm boards are never supported in mainline out the box. .. this is setting a new precident almsot :p Jan 03 01:35:18 One must be careful with new precidents... or at least something :D Jan 03 01:38:35 lol GenTooMan Jan 03 01:51:22 with precedents often come ridiculous expectations. Jan 03 01:55:03 ah .. expectations and assumptions .. the enemy of all systems and projects Jan 03 02:06:02 watch out for the pundit speculators. The bein of getting anything done right. Jan 03 02:07:02 it's like they run out and do unproductive thinking as soon as anything is accomplished not even caring how much it took to get to point A (never I should say) **** ENDING LOGGING AT Sun Jan 03 02:59:58 2016