**** BEGIN LOGGING AT Fri Oct 02 02:59:59 2015 Oct 02 03:47:42 <_av500_> npoe Oct 02 08:07:35 I tried flashing a new image onto my BBB via sd card as described here; http://www.crashcourse.ca/wiki/index.php/BBB_software_update_process#How_to_update Oct 02 08:08:17 But the LEDs all stayed solid on. So expecting the LEDs to flash actively, I then pressed S3/Power after a couple of minutes but with no avail. Pressing S1/Reset afterwards made the LEDs constantly flash up and down Oct 02 08:08:40 Hooking up my BBB Rev. C via USB doesn't work as it used to before trying to upgrade. Is it bricked now? How can I determine it's status and what can be done to unbrick it? Oct 02 08:14:50 it is not possible to irrevertibly destroy a BBB through flashing Oct 02 08:15:24 It's not oviously not accessible via SSH anymore, it doesn't make a difference whether I boot with the microSD inserted or not. Oct 02 08:15:42 I suspect the up/down pattern is what you want, I guess and then you wait until it stops Oct 02 08:16:46 That was going to be my next question: Is there any documentation on the LED codes/patterns? I can't seem to find something useful Oct 02 08:17:18 the led pattern during flashing has changed over time Oct 02 08:17:24 Sadly, I don't have the hardware to access the BBB via serial to see what it's doing Oct 02 08:18:52 you should consider getting one of those usb-serial things. they are dirt cheap Oct 02 08:19:03 anyway, I'd suggest you try this: Oct 02 08:19:07 power off BBB Oct 02 08:19:15 insert the card with flashing image Oct 02 08:19:21 tbr: It's already being shipped to me right now. Oct 02 08:19:39 hold down the user button Oct 02 08:19:50 connect power, while still holding the button Oct 02 08:20:02 user/boot button is S2, right? Oct 02 08:20:03 after some random flashing it should go into a steady pattern Oct 02 08:20:13 * tbr goes to get his bbb Oct 02 08:20:32 yes Oct 02 08:20:35 ta Oct 02 08:20:54 I'm not sure if the pattern will stop once flashing is done Oct 02 08:21:03 leave it running for ~15-20min Oct 02 08:21:18 after that remove power, remove card Oct 02 08:21:31 power up board and leave it running for >10min Oct 02 08:21:49 on first boot the usb functionality can be seriously delayed Oct 02 08:22:03 and if you power it down during that time it might screw up the installation Oct 02 08:23:35 While holding S2 and powering the BBB, the LEDs flashed rapidly for about 1s. Now only PWR and User LED 2/D4 are on steadily. Oct 02 08:25:33 btw: you can let go of s2 once the initial pattern appears Oct 02 08:26:00 tbr: I did let go of S2 as soon as the steady pattern appeared. Oct 02 08:26:41 are some of the leds flickering? Oct 02 08:26:53 http://www.crashcourse.ca/wiki/index.php/BBB_software_update_process#How_to_update says "[...] hold down the Boot button, apply power and continue to hold down the Boot button until the first LED comes on" Oct 02 08:27:05 yeah Oct 02 08:27:22 What is the first LED? PWR? User 0/D2? Oct 02 08:27:36 any of the 4 in the group Oct 02 08:27:44 Ok Oct 02 08:28:21 the button shorts one of the sysid pins that changes boot order during ROMBL Oct 02 08:28:23 2/D4 is still on, steadily. No flashing/blinking. Oct 02 08:28:33 and that's like within the first split second of power up Oct 02 08:28:43 tbr: Thankfs for the info. Oct 02 08:29:09 not sure what to make of that. maybe you should try and redo the card? Oct 02 08:29:23 make sure to write the image to the device, not a partition Oct 02 08:29:46 The card is perfectly fine, checksum is correct, uncompressed .img written to raw device Oct 02 08:31:35 The very first time I tried flashing the image I followed the same procedure, resulting in all four user LEDs being on steadily. Now I did the same and only 2/D4 is on - On both tries I did *not* get any flashing pattern. Oct 02 08:32:33 and which image is it? Oct 02 08:33:22 As already said earlier, I waited ca. 5min when having all four LEDs on. I then pushed Power/S3 once but with no avail. Pushing Reset/S1 afterwards seemed to have rebooted the BBB which resulted in the user LEDs going up and down periodically. Oct 02 08:34:50 tbr: 2015-09-27 Jessie Snapshot Flasher lxqt-4gb BBB/G 4GB eMMC Oct 02 08:35:53 mhm, try pressing reset again. maybe you get the pattern? Oct 02 08:36:09 Btw, my BBB is still in the same appearent state: 2/D4 only. Oct 02 08:36:21 I'll press S1 once now. Oct 02 08:37:13 LEDs turned off, all showed up together once, now it's doing the what I call staircase pattern. Oct 02 08:37:35 knight rider like? IIRC that's what flasher is supposed to do Oct 02 08:38:09 LEDs are going up and down between 0/D2 and 3/D5. Oct 02 08:38:13 yup Oct 02 08:38:54 tbr: Yeah, KITT's trying to talk to me here ;) Oct 02 08:39:06 leave that running for a while Oct 02 08:39:10 Will do Oct 02 08:39:16 if it stops that should mean 'done' Oct 02 08:39:19 Thanks for your help, tbr. Oct 02 08:39:21 np Oct 02 08:39:49 But I'm still curious why the BBB did not enter this state automatically as it's supposed to to. Oct 02 08:39:50 it's a bit of guessing as the leds are used inconsistently with the images and I don't flash mine that often Oct 02 08:40:01 that is indeed a bit of a mystery Oct 02 08:40:25 you could try asking rcn-ee if he turns up here or on the google group thingy Oct 02 08:40:44 This is my second attempt to flash the BBB ever. On my first try I followed the official guide(s) *to the letter*. Oct 02 08:40:58 tbr: Cheers, will do. Oct 02 08:41:43 np, yw Oct 02 09:36:37 My BBB is alive again, SSH isn' working anymore, though. Connection refused on Port 22, but this likely a problem with the snapshot image. Oct 02 09:39:04 weird though Oct 02 09:39:42 try rebooting one more time, maybe it didn't start because of key generation or such? Oct 02 09:40:04 also there should be cdc-acm, so you can get a serial console Oct 02 09:40:07 Yeah, will do Oct 02 09:40:25 Pressing Power/S3 once doesn't do anything Oct 02 09:40:47 try going in through the serial Oct 02 09:40:54 should show up a ttyACM0 or such Oct 02 09:41:35 tbr: I was just about to try that anyway. It worked Oct 02 09:41:44 :) Oct 02 09:42:25 Just ran poweroff on the BBB, rebooting now. Hopefully SSH works. Oct 02 09:45:46 SSH still doesn't work, I'll fix it using serial connection now. Oct 02 09:45:58 tbr: Thanks again, I'm really glad my BBB is running again :) Oct 02 09:54:29 Meh, keys appear to be missing on the BBB Oct 02 09:57:52 hello can anyone help me wyt a problem regarding the beagle bone Oct 02 09:58:00 with * Oct 02 09:59:23 mihain: Just state your problem being as descriptive and detailed as possible. Someone will eventually respond Oct 02 10:01:23 I am running a jar on the beagle bone and using http://libbulldog.org/ to capture some serial data and send over ip to another device, it works great but after some time I get a Killed message on the putty console or the cloud9 one how can I make it run endesly .... the software has a built in loop for that but by some means the beagle decides to kill my process I think Oct 02 10:04:35 jar? so java? Oct 02 10:04:55 maybe some sort of memory leak and the OOM-killer just slays your process? Oct 02 10:05:08 dmesg might have details Oct 02 11:05:34 thank you dmesg resulted in [270303.527481] Out of memory: Kill process 25557 (java) score 430 or sacrifice child [270303.535428] Killed process 25557 (java) total-vm:412140kB, anon-rss:233364kB, file-rss:4kB Oct 02 11:05:46 bingo Oct 02 11:06:18 you might want to either tune your memory consumption in java or ditch java completely and use something that uses less memory Oct 02 11:06:24 Now I have to see if it's from the java code or the libbulldog rx tx library Oct 02 11:06:42 do you know a good reliable serial library for java on the BBB Oct 02 11:09:34 I would personally elimiate java from the equation, with a vengeance Oct 02 11:09:48 can't ditch java becuse of the job at hand that requires cross platform development Oct 02 11:10:14 "good luck" Oct 02 11:10:21 :)) Oct 02 11:10:40 btw: I trust your BBB image is completely minimal? Oct 02 11:10:49 Thank you - more sleepless nights again Oct 02 11:10:59 and you didn't use the standard debian image that drags in a desktop environment and all that Oct 02 11:11:32 running debian 2015-03-01\ Oct 02 11:11:55 how can i drag it to the desktop enviroment Oct 02 11:12:17 if you used the standard debian image you have a whole desktop experience in it Oct 02 11:12:24 → bad for your free memory Oct 02 11:12:34 you want a console image Oct 02 11:13:00 I an using the cloud nine browser interfece Oct 02 11:13:16 I only need simple command to execute the jar Oct 02 11:13:29 dear god... Oct 02 11:13:43 https://rcn-ee.com/rootfs/2015-09-11/flasher/ - use the 8.2 debian console image Oct 02 11:13:51 I was thinking of a way to run the code remoteley from eclipse on the beagle so that I could have debug Oct 02 11:14:27 that's a flasher image. if you want a SD image it's somewhere else on that server Oct 02 11:14:40 thank you for the link I'll give it a try Oct 02 11:15:06 no it's perfect I want it to run from the emmc to reduce operating costs Oct 02 11:18:29 you could check if eclipse can execute things over ssh. if yes then this would be a way to start your code and debug it. Oct 02 11:59:44 I'm now flashing the 2015-03-01 stable image (currently running 2015-09-27 snapshot). This time, the flashing process works exactly as described. I push and hold Boot/S2 before powering on the BBB with sd card inserted. The LEDs start flashing as expected as mentioned in the official guide, no need to press Reset/S1 after all steady LEDs to initiate actual flashing. Also, LED pattern is different this time, no Oct 02 11:59:50 KITT/staircase but low, very rapidly blinking, almost steady 2/D4 and normal blinking 0/D2 here Oct 02 12:00:52 yeah, that's more like normal operation pattern Oct 02 12:00:56 Well, at least I expect it to be flashed currently. I'll just wait whatever it takes for the LEDs to become steady again (not longer than an hour, though). Oct 02 12:01:14 20min should be enough Oct 02 12:01:30 if you have usb plugged, you might be able to use the serial console Oct 02 12:01:50 The guide says " Oct 02 12:02:06 At that point, just sit back for about 45 minutes and watch the flashing LEDs until they all come on solid." Oct 02 12:02:12 ok Oct 02 12:02:14 Let's see. Oct 02 12:07:15 Done. Oct 02 12:11:05 Actually, the LEDs never went all solid Oct 02 12:11:24 * tbr takes a me(n)tal note ;) Oct 02 12:12:04 But I can successfully log in via serial or SSH (new keys), everything looks like it's back to 2015-03-01 again. Oct 02 12:13:25 This really confuses me, no matter which way I went, there was always an undocumented step or something *not* happening when it actually should. Oct 02 12:14:23 Is there any way to tell if the BBB is still flashing besides looking at the ever changing LED patterns? Oct 02 12:15:22 It appears to me there is now way to verify the flash process is successfully over. Since the guide says I had to wait 45min. but everything looked fine after 5min. already. Oct 02 12:15:58 yeah, normal Oct 02 12:16:07 it's because of impatient people Oct 02 12:17:46 So those 45min. are actually just a hugely overestimated amount of time to make sure flashing is definitely done before further user interaction? Oct 02 12:17:56 yes Oct 02 12:19:34 Do I still need to power off the BBB before removing the sd card? Oct 02 12:19:54 you can see that all the leds turn of one thefalshing is complete from what I have seen Oct 02 12:20:04 It's still plugged in and I haven't rebooted yet after initiating the flash process and loggin in via SSH. Oct 02 12:20:42 then it's booted from sd Oct 02 12:20:48 yes it's advisable that you do so Oct 02 12:20:50 I'd recommend to issue a shutdown Oct 02 12:21:17 note that the ssh fingerprint will now change once more and first boot might take long Oct 02 12:21:42 Hm, maybe it never flashed and just booted from sd, hence why everything was so fast. Oct 02 12:21:48 tbr: Sure. Oct 02 12:22:15 to flash be sure to hold the button next to the sd card while you power on the beagle Oct 02 12:22:58 once the 4 leds start flashing after 5-10 sec you can relaese the button and wait for all of them to turn off flashing complete Oct 02 12:47:36 mihain: I already flashed successfully, but thanks for stating it again. Oct 02 12:48:25 The thing is that I followed the official guide to the letter and the LEDs did *not* flash but stayed all solid. I actually had to press Reset/S1 once to initiate the flash process. Oct 02 12:48:34 I was afk. I'll reboot now. Oct 02 12:51:11 Yup, nothing was flashed, it just booted from sd. Oct 02 12:53:04 you need to shutdown Oct 02 12:53:16 just a reboot will boot into the SD and restart flashing Oct 02 12:53:40 as a warm boot retains the sysid configuration, which points to the SD due to initial button press Oct 02 12:53:57 tbr: I shut it down, removed the sd, booted up and got into my "old" 2015-09-27 installation. Oct 02 12:54:26 did you really use a flasher image then? Oct 02 12:54:35 or did you just have an SD image Oct 02 12:55:27 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_lxqt Oct 02 12:55:42 the image with md5sum f814... Oct 02 12:55:58 It's clearly a flasher image for my 4gb BBB rev. C Oct 02 12:58:28 For 2015-03-01 I used http://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz Oct 02 12:59:36 Extracted the image and wrote it do my sd card (raw device, no partition). It's obviously working since the BBB boots from it whereas it's supposed to flash this image onto eMMC. Oct 02 13:00:45 I then followed http://www.crashcourse.ca/wiki/index.php/BBB_software_update_process#How_to_update to the letter. Oct 02 13:00:59 kl3: no "flasher" in the image name Oct 02 13:01:27 kl3: you can execute the flashing process from a script in opt or such manually, but I'm not sure how reliable that is Oct 02 13:03:39 tbr: Ah, my fault. I copied the URL to the 2015-03-01 file from http://beagleboard.org/latest-images instead of http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29_4GB_eMMC_Flasher Oct 02 13:20:10 Alright, KITT pattern this time again. Oct 02 17:48:23 My Beaglebone Black seems to be bricked. I've tried flashing the rom with the most current image, but all I ever get is the blue power light Oct 02 17:50:42 I seem to have a bricked BBB, all I get is the blue power light. I've tried flashing with the newest image. Any suggestions? Oct 02 17:50:46 becca_MathWorks, http://elinux.org/BeagleBoardUbuntu#Flasher did you try this? Oct 02 17:51:18 works for me with a deleted eMMC Oct 02 17:52:17 Yes, that's exactly what I tried Oct 02 17:52:31 hm Oct 02 17:54:03 Yup, not sure what to try Oct 02 17:56:09 becca_MathWorks: what did you do before that? Oct 02 17:57:24 Not sure, it's a shared device and no clue who had it last. It was on our hardware shelf Oct 02 17:57:49 Unboxed it, tried to boot it, didn't get any user LEDs started the flash process. Couldn't get the flash to trigger Oct 02 17:58:04 well, the previous person might have killed it for good Oct 02 17:58:38 if only the led next to the barrel connector comes on, then something is very wrong. Oct 02 17:58:51 happen to have a USB-serial device to plug into the debug port? Oct 02 17:58:53 hrm Oct 02 17:59:09 Yea, I can grab a USB-serial adaptor Oct 02 17:59:33 brb Oct 02 18:03:31 which pins out of the DB9 do I need? Oct 02 18:03:53 do NOT connect RS232C to the debug port under any circumstances Oct 02 18:04:52 levels wrong? Oct 02 18:05:09 yes Oct 02 18:05:51 needs to be 3.3V UART Oct 02 18:06:13 hrm okay Oct 02 18:08:51 btw: are you sure you wrote the flasher image to the raw device and not to a partition? Oct 02 18:09:16 aka /dev/sdX or /dev/mmcblkX Oct 02 18:09:54 and not /dev/sdX1 or /dev/mmcblkXp1 Oct 02 18:13:57 Okay, got the right cable Oct 02 18:14:19 tbr: I used win32flasher to write the image to the device Oct 02 18:15:12 becca_MathWorks: ah, windows. that /should/ get it right Oct 02 18:15:46 becca_MathWorks: well, hook it up, set it to 115200 8n1 and see if you get "CCCCCCCC" on the terminal Oct 02 18:16:10 if you don't even get that, then the board is dead Oct 02 18:16:14 I'm downloading the drivers for the cable now, just to double check, I'm using this cable: http://www.adafruit.com/product/954 Oct 02 18:17:13 yes, but do NOT connect the power pin Oct 02 18:17:24 just RX,TX,GND Oct 02 18:17:59 thanks Oct 02 18:19:32 Pin 1 on the board is the keyed pin (the one with the dot)? Oct 02 18:24:38 that's odd, putty won't let me set flow control to none Oct 02 18:29:38 Yea, won't connect it seems Oct 02 18:31:29 if you don't see output, then it's dead Oct 02 18:31:45 Well, that's a drag Oct 02 18:32:47 you could still try a different "known working" card Oct 02 18:34:14 Yea, I'll see if anyone has one laying around Oct 02 18:36:41 I have a different board that's working. Maybe I'll try to flash it and test the card that way Oct 02 18:37:26 yes Oct 02 18:52:54 Hello everyone Oct 02 18:53:31 Looking for help in a project I want to do. Oct 02 18:56:29 you might want to be more specific Oct 02 18:56:56 It is a project related with a vacuum robot Oct 02 18:57:26 I landed in this site because of the boards that are available here. Oct 02 18:57:40 which I think they will give me a lot of help Oct 02 18:57:56 So the new board is taking the flash just fine, how do I know when it's done though Oct 02 18:58:17 becca_MathWorks_, all 4 leds are on Oct 02 18:58:24 thanks Oct 02 19:04:43 Hi all Oct 02 19:04:55 The BBB has audio input and audio output? Oct 02 19:14:36 <_av500_> no Oct 02 19:24:27 hello everyone Oct 02 19:25:53 someone interested in a project Oct 02 19:26:41 so I can't connect to the debug port even on the board that's working Oct 02 19:30:49 becca_MathWorks_: try reversing TX/RX Oct 02 20:23:56 Do you know a very good (audio quality) cape for audio input/ouput for the BBB? Oct 02 21:06:07 disunity Oct 03 02:01:56 hi i'm a little confused Oct 03 02:02:36 with the modes for the gpiomux, can you set the mode individually for each pin? i'm after 38 gpios and i2c **** ENDING LOGGING AT Sat Oct 03 02:59:58 2015