**** BEGIN LOGGING AT Wed Jan 31 03:00:03 2018 Jan 31 04:20:01 Hi.. I have restored an image from a backup on new BBBWireless. After restore i can see the heartbeat of LED but i am unable to ssh using 192.168.7.2. Also My device does not appear in Device manager not in network adaptors. How can I get it back? Jan 31 04:20:58 any suggestion?? Jan 31 04:49:37 LordSAK: do you have a console cable to see what's happening on boot? Jan 31 06:01:47 I have the new BBX15 but have some issues on powering up Jan 31 06:01:54 I dont see any display in the HDMI Jan 31 06:02:17 on connecting the serial debug to PC, I don't see any meaning ful text in teraterm GUI Jan 31 06:02:38 I have used the right baudrate and serial port config but still no meaning ful text Jan 31 06:02:48 anyidea what am I missing Jan 31 06:49:46 Hi.. I have restored an image from a backup on new BBBWireless. After restore i can see the heartbeat of LED but i am unable to ssh using 192.168.7.2. Also My device does not appear in Device manager not in network adaptors. How can I get it back? Jan 31 07:22:12 Guest79908: what non-meaningful output do you see? you can use pastebin.mozilla.org to share Jan 31 07:22:37 LordSAK: connect to the debug uart Jan 31 07:23:36 Sorry I forgot to mention But BBBW is somewhere else and I cant physically do anything with it Jan 31 07:23:49 I only have usb serial and LAN cable Jan 31 09:38:40 Hi guys, I am still trying to figure out the boot issue with beaglebone blue, the bootlog can be found here https://pastebin.com/KaTJS7gf Jan 31 09:39:06 Any help would be really appreciated as I am new to the Beaglebone enviornment Jan 31 10:11:36 LordSAK: how on earth do you even "restore an image from a backup" on a beaglebone to which you have no physical access Jan 31 10:14:10 Daksh: filesystem is corrupted Jan 31 10:15:06 you can try to repair it with e2fsck /dev/mmcblk1p1 Jan 31 10:15:52 I should use this command straight after (initramfs)? Jan 31 10:16:04 yes Jan 31 10:16:38 I will give it a try... if this does not work? will I have to get a new image for the os? Jan 31 10:17:16 I'd strongly recommend reflashing eMMC regardless Jan 31 10:17:53 attempting to recover the filesystem may be useful to recover any files of relevance you may have on the beaglebone Jan 31 10:18:08 will I be able to recover some of my work in the home directory? or am I write in assuming that reflashing will delete everything ? Jan 31 10:18:39 reflashing will delete everything, so my suggestion would be to try to recover the filesystem using fsck first Jan 31 10:19:43 if it doesn't boot after fsck completes, you may still be able to recover files by booting from sd card and then mounting eMMC Jan 31 10:20:15 it'll all depend on how badly the filesystem got corrupted Jan 31 10:20:25 yeah I am trying that now... and I was also wondering what could be the possible reasons that led to this corruption? is there anything obviuosly stupid that I did? Jan 31 10:22:00 assuming you didn't mess with /dev/mmcblk1 directly, my first guess would be frequently powering off the board without properly shutting it down Jan 31 10:22:17 what was the last thing you did before this happened? Jan 31 10:23:48 I had been doing quite a few things actually... one mistake I did was powering the 6V servo rails on when the device was connected to the usb ... another thing I tried was connecting a battery to the microusb port Jan 31 10:24:13 it was working fine even after that but suddenly it just stopped Jan 31 10:24:25 euhh Jan 31 10:26:14 okay I tried that command you told me Jan 31 10:26:52 powering on the 6V rail on without V_BATT present will simply do nothing, it shouldn't be harmful Jan 31 10:27:23 now the final two lines say... rootfs ***FILE SYSTEM WAS MODIFIED*** Jan 31 10:27:45 okay good Jan 31 10:28:02 so what does that mean? should I try rebooting? Jan 31 10:28:04 now type reboot Jan 31 10:28:52 I did... (intrafamfs) reboot Jan 31 10:29:03 and now I get (intramfs) Jan 31 10:29:07 that's it Jan 31 10:29:14 didnt do anything Jan 31 10:29:15 reboot doesn't work in initramfs? grr Jan 31 10:29:44 use the "sync" command and press the reset button I guess Jan 31 10:29:55 cool trying that Jan 31 10:30:51 it works Jan 31 10:30:56 thank you so muchhh Jan 31 10:30:59 what did you mean by "connecting a battery to the microusb port", like, an usb battery pack? Jan 31 10:31:08 yeah I did that Jan 31 10:31:29 assuming it can provide decent current, that should be fine for powering the board Jan 31 10:31:58 although it's not a replacement for connecting an actual 2S battery pack to the designated terminals Jan 31 10:33:13 e.g. the 6V output and the motor outputs only run off the battery pack Jan 31 10:33:55 not off usb Jan 31 10:35:17 I guess it's possible they may also run off the 12V DC input (the barrel connector), not sure about that Jan 31 10:45:59 Hi sorry my chrome crashed, I was wondering then was it connecting the battery to the microUSB corrupted my system? Jan 31 10:46:15 I don't see how Jan 31 10:46:42 please have some patience when asking questions, don't send private messages Jan 31 10:47:48 here's the chunk of irc log you missed: https://pastebin.com/raw/4FBNkXCU Jan 31 10:49:10 cheers zmatt... this was very helpful... still trying to learn... many lessons learnt todays Jan 31 10:50:04 and to power down the system in future I guess I should be using the POW button to shut it down safely? Jan 31 10:50:49 yeah, although when I said that I hadn't realized yet that you were using a beaglebone blue, which slightly complicates the situation Jan 31 10:51:31 how does it complicates it? I thought beaglebone blue = beaglebone black + robotics cape Jan 31 10:53:59 so basically everything should be similar to bbblack Jan 31 10:54:00 I don't know what's on the robotics cape exactly, but the power scheme of the blue is rather complicated. shutting down while V_BATT (battery pack) or VCC (barrel connector) is powered causes various 5V outputs to remain powered (the one on the power header, on the GPS header, usb host port), which means you have to be rather careful to ensure that this doesn't power any external logic that drives a signal Jan 31 10:54:06 into the BBB Jan 31 10:56:14 also I'm concerned about the analog inputs that are used to monitor V_BATT and VCC, although the current injected while in shutdown state is limited by a series resistor hence hopefully won't quickly damage anything Jan 31 10:58:46 I will surely keep that in mind for future design... I don't think there was any external signal coming into the BBB... I will thoroughly check again... how do you suggest I turn the board off when an emergeny button is used by the user? because cutting of the power does not seem like a good option now Jan 31 10:59:00 should I send a shut down command using the terminal? Jan 31 11:01:34 performing a clean shutdown is definitely best for the eMMC, even if it means having to be a bit careful with the hardware connected to the bbb Jan 31 11:01:51 ideally avoid being in shutdown state with V_BATT or VCC supplied for extended amounts of time Jan 31 11:02:46 alternatively, you can try to harden the eMMC against power loss. this is something we do since we can't expect clean shutdowns for our products. Jan 31 11:04:13 we reconfigure the eMMC into SLC mode with reliable writes enabled. This should make it more resilient against power loss, increase reliability/durability overall, and even increases performance. However in exchange, it sacrifces 50% of the storage capacity of eMMC Jan 31 11:04:35 zmatt There is a guy who is handling stuff on my behalf. But he dont have that much knowledge of ports and pins etc Jan 31 11:05:11 Even I am not sure i will able to guide him about FTDI Jan 31 11:05:20 Storage is not an issue. So is there a guide or datasheet on how to reconfigure emmc I could follow? Jan 31 11:06:49 Daksh: I have a branch of the mmc-utils project with a custom command added for that specific purpose: https://github.com/dutchanddutch/mmc-utils/commit/custom Jan 31 11:08:44 be sure to carefully read the commit message Jan 31 11:10:03 LordSAK: if you can't interact with the beaglebone nor even describe what was done to it, I would say the chances of us being able to help you are roughly 0% Jan 31 11:10:49 thank you so much zmatt. My first step now is to recover my code on Beagle and put it on github and after that I will go through your code and understand how it works. You have been really helpful. Thank you very much Jan 31 11:11:37 Daksh: mmc-utils already has commands to perform the things this command does, but they are difficult and error-prone to use Jan 31 11:11:48 which is not ideal when dealing with commands that have irreversible effects Jan 31 11:12:04 that's why I added this command which performs a lot of checks and then performs the necessary steps Jan 31 11:14:59 anyway, I have to go now Jan 31 11:19:45 Well. I took a backup from one BBBW in a new micro SD and used that microSD to my target BBBW. I connected the USB and it started to restore same way as we did before for another BBBW. After 10mins it was restored(I think) because i got the heartbeat pattern. But it never showed up to my laptop. I used this link for backup and restore: https://stackoverflow.com/questions/17834561/duplicating-identical-beaglebone-black-setups Jan 31 11:20:10 BTW these same steps worked on other BBBW in same conditions(Remotely using that guy) Jan 31 11:20:22 I can fill in with additional info if needed Jan 31 11:20:39 do ask me if i have missed something Thanks zmatt Jan 31 11:21:14 here is the command just in case Jan 31 11:21:24 sudo /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh Jan 31 11:42:24 zmatt: Thanks for the help.. Just fixed it :D Jan 31 11:59:00 Hi Jan 31 11:59:35 facing some problems here, cant realy get my BBB to connect to my Computer throu the USB port Jan 31 11:59:45 via NDIS/USB Tethering Jan 31 12:00:07 it doesnt even show up in the device manager Jan 31 12:00:11 cabling is ok Jan 31 12:00:23 (with datalines ofc) Jan 31 12:01:37 anyone faced the same problem? Jan 31 12:11:08 hey JanHenrik I had a similar problem... did you try the uart debugging over usb and get a bootlog? I did that and it seemed like the system files were corrupte and then I ran fcsk command to repair... and it worked perfectly Jan 31 12:11:21 I would suggest you to start with getting a bootlog Jan 31 12:13:04 Thank you zmatt for your previous replies. I still need to educate myself more on mmc-utils... I will read more and try to understand it... Jan 31 12:17:03 Thanks Daksh Jan 31 12:17:07 I will try so Jan 31 12:24:58 hello, i use energia on a ubuntu 16.04 LTS distro and have a Rev. 1.5 with a 2553 chip. programming works, simple examples like blink work. however i have problems with the serial monitor. yesterday evening it worked for some time. today it doesn't. i read about the kernel patch but this is for kernel versions 2 and 3. i am using version 4. how should i proceed. thank you! Jan 31 12:26:41 what i already tried: Jan 31 12:28:55 1. using sw uart instead of hw uart by changing jumpers from horizontal to vertical. 2. adding my user to the right groups. 3. using a different serial program for reading. Jan 31 12:29:54 4. pressing the reset button on the launch pad until ACM0 is detected Jan 31 12:47:25 uhh, what kind of device are you even talking about? Jan 31 12:52:12 I googled "enegia 2553" and it seems to be a variety of MSP430, which has me even more confused Jan 31 12:54:54 serialproblem: do you actually have a question related to a beagleboard or beaglebone device? if not, how exactly did you end up here? Jan 31 13:20:38 oh, i'm sorry Jan 31 13:22:02 http://energia.nu/contact.html Jan 31 13:24:13 there i pressed "Connect to freenode IRC" Jan 31 13:24:21 do not know why i ended up here Jan 31 13:24:23 sorry Jan 31 13:27:07 because they fucked up the link, lol Jan 31 14:56:04 can I use beaglebone as a development board and program drivers for cortex A8? Jan 31 14:56:31 beaglebone black rev c Jan 31 15:07:10 uhh, it has a cortex-a8. i'm not sure what exactly you're asking Jan 31 15:07:38 whether you can use it as a development board to program drivers seems to be more a question about you than about the board :) Jan 31 15:08:04 I'm also not sure what you even mean by "drivers for cortex-A8" Jan 31 15:08:25 http://www.st.com/en/evaluation-tools/stm32f4discovery.html Jan 31 15:09:05 this is one of the development board based on ARM cortex M4 Jan 31 15:09:27 so we can make binaries and flash it to the board Jan 31 15:09:34 we can actually work on Jan 31 15:10:15 CMSIS level, using the it's API's we can develop the drivers and access USART, I2C etc Jan 31 15:11:52 so instead using linux kernel and developing general purpose application, I want to work on processor specific features Jan 31 15:14:27 using linux does not exclude using processor specific features Jan 31 15:27:55 if you want to use baremetal development, you can use the beaglebone for that too (e.g. in combination with TI-RTOS or StarterWare), though you'll want to solder on the jtag header Jan 31 15:28:27 but driver development with linux seems more difficult but I am just a beginner. Jan 31 15:29:30 most peripherals already have drivers Jan 31 15:33:01 yeah, I know but I am new to driver development and for getting started I need to play with processor specific header files and CMSIS core APIs Jan 31 15:33:42 Hello all, I ran htop on my BBBlue and noticed around 5 processes all having the script address: /usr/bin/nodejs autorun.js (not quite sure about the nodejs bit), and all were taking around 7% of CPU Mem each. I wanted to know if these processes are required , and what are they? Jan 31 15:36:02 krish-iyer: CMSIS is a thing for cortex-M processor, not cortex-A Jan 31 15:37:29 yeah I also saw now they are more suitable for hosting OS platforms Jan 31 15:39:20 does anyone know what that script is? Jan 31 15:39:24 what is it needed fo? Jan 31 15:40:12 for* Jan 31 15:54:00 maybe someone does, but now you'll never know Jan 31 17:14:35 Just a quick question, what book is good to start learning Beaglebone? Jan 31 17:15:46 BBB.io/books. Jan 31 17:16:23 I recommend BeagleBone Cookbook and Exploring BeagleBone Jan 31 17:18:33 Thanks **** ENDING LOGGING AT Thu Feb 01 03:00:03 2018