**** BEGIN LOGGING AT Fri Dec 25 03:00:10 2020 Dec 25 12:36:54 I just purchased a bbai and updated the image. Cloud9 will not start, searched the web and found nothing. Any help out there? Dec 25 12:43:14 Hello... beagleboard.org/latest-images Dec 25 12:43:27 You may need to update your image. Dec 25 12:43:47 Oh. Dec 25 12:43:51 Sorry. Dec 25 12:43:57 I misread what you typed. Dec 25 12:44:07 beagleboard.org/upgrade Dec 25 12:44:10 Try that one. Dec 25 12:45:11 beaglebone.local:3000 is one way to get there or you can type in your IP Address:3000. Dec 25 12:48:03 Or...if on Win, 192.168.7.2:3000. If on linux and you typed in ssh debian@192.168.7.2, then 192.168.7.2:3000. Dec 25 12:48:58 brb Dec 25 12:53:29 I type in http://192.168.1.58/ide.html -- "502 Bad Gateway" is the result, same with ipaddr:3000 Dec 25 12:54:09 3000 Dec 25 12:54:13 Oh. Dec 25 12:54:26 Did you try :3000 for the port? Dec 25 12:54:34 Oh. Dec 25 12:54:36 Okay. Dec 25 12:54:43 Hmm. Dec 25 12:55:17 what does uname -a show? Dec 25 12:55:24 and cat /etc/dogtag? Dec 25 12:55:24 I don't understand. It worked before the flash and now it does not. Dec 25 12:55:53 Linux beaglebone 4.14.108-ti-r131 #1buster SMP PREEMPT Tue Mar 24 19:18:36 UTC 2020 armv7l GNU/Linux Dec 25 12:56:00 Okay. Dec 25 12:56:17 cat /etc/dogtag Dec 25 12:56:28 BeagleBoard.org Debian Buster IoT TIDL Image 2020-04-06 Dec 25 12:56:51 Hmm. Yep. You have the updated versions. Did you update/upgrage yet? Dec 25 12:57:17 yes Dec 25 12:58:11 Hmm, did you try that beagleboard.org/upgrade site to update the software on the board? Dec 25 12:58:15 Oh and... Dec 25 13:00:10 Yes I did -- AM5729 Debian 10.3 2020-04-06 8GB SD IoT TIDL Dec 25 13:00:40 what does df -h show? Dec 25 13:01:01 For your partition? Dec 25 13:01:10 Filesystem Size Used Avail Use% Mounted onudev 199M 0 199M 0% /devtmpfs 62M 2.8M 59M 5% /run/dev/mmcblk1p1 15G 3.7G 10G 27% /tmpfs 307M 8.0K 307M 1% /dev/shmtmpfs 5.0M 4.0K 5.0M 1% /run/locktmpfs 307M 0 307M 0% /sys/fs/cgroup/dev/sda1 15G 42M 14G Dec 25 13:01:11 1% /mnt/datatmpfs 62M 0 62M 0% /run/user/1000 Dec 25 13:01:23 messy Dec 25 13:01:27 Okay. I see. Dec 25 13:01:56 It seems you only have 42MB left on the eMMC? Dec 25 13:02:02 Are you using eMMC? Dec 25 13:02:32 Or SD Card? Dec 25 13:02:53 yes and eMMC -> /dev/mmcblk1p1 15G 3.7G 10G 27% /only 27% used Dec 25 13:03:01 Oh. Okay. Dec 25 13:03:18 Oh. I see it now. You are right. Dec 25 13:03:36 I might have to plug mine in. Dec 25 13:03:40 Please hold. Dec 25 13:03:45 I will boot mine. Dec 25 13:03:50 Not going anywhere Dec 25 13:03:57 More Coffee Dec 25 13:04:25 Ha. Dec 25 13:04:39 What OS are you using on your HOST? Dec 25 13:04:47 debian buster Dec 25 13:04:52 Okay. Dec 25 13:05:39 Dang it. Let me try to connect to c9. Dec 25 13:05:57 I say dang it b/c I have another image on my board right now. Dec 25 13:06:32 aargh! Dec 25 13:06:46 It is okay. Dec 25 13:06:48 I am connecting. Dec 25 13:06:52 I got there on the board. Dec 25 13:07:18 Hmm. Dec 25 13:07:51 This is odd. Dec 25 13:08:30 I wonder if there are any journalctl -x showing errors on your board? But, use a pastebin.com paste for this output. Dec 25 13:08:48 Please. I will show you my image. Dec 25 13:08:55 in the meantime. Dec 25 13:09:22 BeagleBoard.org Debian Buster IoT Image 2020-11-16 Dec 25 13:09:35 Hmm. Dec 25 13:09:47 Maybe the TIDL image does not have c9 on it? Dec 25 13:10:18 I guess that is a posiblilty, but why? Dec 25 13:10:26 Try to go to /etc/nginx/default to look through the file and see if your nginx shows port 3000 on it for cloud9. Dec 25 13:10:35 looking Dec 25 13:10:39 Okay. Dec 25 13:11:28 And maybe using the "prescribed" linux IP Address may prove useful too. Dec 25 13:11:33 Just a thought. Dec 25 13:12:02 192.168.6.2 or 192.168.7.2 or 192.168.6.1. Dec 25 13:13:03 nginx/default does not exist Dec 25 13:13:14 I could connect before the image update Dec 25 13:13:40 Hmm. /etc/nginx/default ? Dec 25 13:13:49 It is a file. Dec 25 13:13:57 yes and it does not exist Dec 25 13:14:00 Okay. Dec 25 13:14:24 Let me run some checks on my system. Dec 25 13:14:46 Oops. Dec 25 13:15:08 try /etc/nginx/sites-available/default Dec 25 13:16:01 farside: I know I am stressful to deal w/ right now. Please forgive me. Dec 25 13:16:20 I just got up and saw the post. Dec 25 13:16:24 not a problem - just found that file Dec 25 13:16:59 It should show a localhost for cloud9 at port 3000. Dec 25 13:17:44 #RCNEE-start: location / { #Cloud9 proxy_pass http://localhost:3000; } Dec 25 13:17:55 Okay. Dec 25 13:18:07 are you sure you are online? Dec 25 13:18:10 Sorry. Dec 25 13:18:16 w/ the new image? Dec 25 13:18:25 yes I am Dec 25 13:18:27 Okay. Dec 25 13:19:02 Are you using Chrome or Firefox? Dec 25 13:19:07 palemoon Dec 25 13:19:12 Oh. Dec 25 13:19:18 I'll try firefox Dec 25 13:19:21 Okay. Dec 25 13:19:39 same result Dec 25 13:19:46 Dang. Dec 25 13:20:06 That is odd. Maybe another person will show you some other ideas to help you on your journey. Dec 25 13:20:14 I do not know right now. I will keep thinking. Dec 25 13:20:31 thanks for the help, not giving up. Dec 25 13:20:37 Okay! Dec 25 13:20:45 Let me go and check some ss commands. Dec 25 13:21:40 https://www.linux.com/topic/networking/introduction-ss-command/ shows some simple commands to test your network. Dec 25 13:21:45 w/ ss. Dec 25 13:22:23 You may want to look for localhost:3000 and see if something is already looking over that connection. Dec 25 13:23:27 ss -t -a Dec 25 13:23:43 May show something that resembles :3000 and a peer address too. Dec 25 13:24:14 does it show ESTAB to the left of your screen? Dec 25 13:25:35 So, if ESTAB is showing, you can look to make sure ssh and localhost are both using the same IP. Dec 25 13:25:42 ss -t -a does not show :3000 in the list Dec 25 13:25:52 Hmm. Dec 25 13:25:55 That is odd. Dec 25 13:26:09 Please hold. Dec 25 13:26:13 I will check some more ideas. Dec 25 13:26:40 Okay. cancel your sign in w/ exit. Then, sign in w/ ssh debian@192.168.72 Dec 25 13:26:59 Sorry. debian@192.168.7.2 Dec 25 13:29:03 ok, I cannot use usb, not enough power from host Dec 25 13:29:11 So. exit, ssh debian@192.168.7.2, sign in again, and try 192.168.7.2:3000. Dec 25 13:29:17 Oh. Dec 25 13:29:33 So, do you have a fan? Dec 25 13:29:56 I have something blowing on the system and temperatures are good Dec 25 13:30:01 Okay. Nice! Dec 25 13:30:39 So, debian Buster for dev. desktop. Got it, wait? Dec 25 13:30:45 You cannot use USB? Dec 25 13:30:51 That is a new one. Dec 25 13:30:52 correct Dec 25 13:30:57 not enough power Dec 25 13:31:22 So, is that the error or you just know your system? Dec 25 13:31:42 Gimme a couple Dec 25 13:31:45 Okay. Dec 25 13:35:46 Will not boot on usb from host Dec 25 13:36:29 Hmm. Dec 25 13:36:43 Did you do anything to the machine while we were chatting? Dec 25 13:36:58 no, just searching for answers Dec 25 13:37:05 Besides updating/upgrading? Dec 25 13:37:11 no Dec 25 13:37:11 Okay. Dec 25 13:37:41 Let me go to the bbb.io/latest-images. I want to make sure you are using that specific image. Dec 25 13:38:05 ok Dec 25 13:38:24 Did you ever boot from the eMMC? Dec 25 13:39:03 netstat -tulpn | grep LISTEN -- shows tcp6 0 0 :::3000 :::* LISTEN - Dec 25 13:39:12 Hmm. That is odd. Dec 25 13:39:22 I have the eMMC configured and I do boot from there Dec 25 13:39:35 Are you on a school or enterprise network? Dec 25 13:39:40 home Dec 25 13:39:43 Hmm. Dec 25 13:40:06 This is odd. I just cannot figure out what is going on. I will keep thinking. Dec 25 13:40:19 ok, I will keep digging Dec 25 13:41:11 So, if you cannot sign in any longer on your host, I say update the image again but I think there is something going on. I just do not know what it may be right now. Dec 25 13:41:45 Oh. Dec 25 13:42:07 can you use pastebin and show what cat /boot/uEnv.txt shows? Dec 25 13:42:38 showing my ignorance -- what is pastebin? Dec 25 13:42:45 A paste service. Dec 25 13:43:00 I use it for pasting articles. Dec 25 13:43:09 Use whatever paste service you choose. Dec 25 13:43:10 I guess. Dec 25 13:43:33 working on it Dec 25 13:43:40 Okay. Dec 25 13:45:03 Do you have USB 3.0 on your dev. desktop? Dec 25 13:45:54 yes Dec 25 13:46:00 pasted to pastebin Dec 25 13:46:07 uEnv.txt that is Dec 25 13:46:12 Please post the link. Okay. Dec 25 13:46:40 https://pastebin.com/D1FG1MKu Dec 25 13:47:07 Okay. Dec 25 13:47:30 There are some .sh files that will update your bootloader. Dec 25 13:47:50 It is located here...wait. Let me make sure I can find them. Please hold. Dec 25 13:48:21 ok Dec 25 13:48:37 I do not understand. Where are all your entries in the /boot/uEnv.txt file? Dec 25 13:48:47 I will show you mine. Dec 25 13:48:51 that's it Dec 25 13:48:58 Hmm. Okay. Dec 25 13:49:06 what should it look like? Dec 25 13:49:36 I will show you. Dec 25 13:51:56 But, a normal system will show something similar. My system is a bit off from the current kernel and image. Dec 25 13:52:30 https://pastebin.com/x45Va3gv Dec 25 13:52:51 what files are in /boot? Dec 25 13:53:19 dirs. and files in /boot? Dec 25 13:53:47 so, ls -l /boot Dec 25 13:54:22 https://pastebin.com/GjR3s4kG Dec 25 13:54:55 Okay. Dec 25 13:55:11 So, you have an .old and a .txt /boot/uEnv.* file. Dec 25 13:55:18 So, Dec 25 13:55:38 I made a copy of the origional for paranoia Dec 25 13:55:44 I think you might want to review what is in .old and put that in .txt and reboot. Dec 25 13:55:45 Ha. Dec 25 13:55:55 Show what it looks like please in a paste. Dec 25 13:55:57 The files are identical Dec 25 13:56:02 Oh. Okay. Dec 25 13:56:51 So, it has to be networking. Dec 25 13:56:56 Not my strong suit. Dec 25 13:57:14 Are you plugged in via battery and WiFi? Dec 25 13:57:32 Power supply and hard connection Dec 25 13:57:37 or are you using a USB 3.0 to connect to your dev. desktop? Dec 25 13:57:38 Oh. Dec 25 13:57:40 Okay. Dec 25 13:57:53 I think the USB C provides networking and power. Dec 25 13:58:02 I am pretty sure. Dec 25 13:58:06 I beleive you may have pointed me in the proper direction. I have somethings to pursue that may give the answer. Dec 25 13:58:14 Okay. Dec 25 13:58:16 You are correct on usb c Dec 25 13:58:20 Okay. Dec 25 13:58:35 Thanks! for your help! I will post the answer if and when I find it. Dec 25 13:58:38 So, you are using UART to connect? Dec 25 13:58:43 Okay. Dec 25 13:58:46 Ethernet Dec 25 13:58:50 Oh. Dec 25 13:58:51 Okay. Dec 25 13:59:15 I suggest reading LPIC2. Dec 25 13:59:23 It is all about networking. Dec 25 13:59:32 OK will do Dec 25 14:00:47 I guess you are having issues b/c of the lack of USB C to USB 3.0. Dec 25 14:01:05 I should have known. Networking! Dec 25 14:04:03 HI Dec 25 14:05:02 I have been facing trouble with BBAI's pin state just after power up. Dec 25 14:06:41 8-9s after power up, DTS takes control and got desired output. But initially 8-9s I'm getting default pin state HIGH. Dec 25 14:54:14 MIIL: pins have default internal pull-up or pull-down (varies per pin) Dec 25 14:55:04 if you want a pin to have a specific level immediately after power-up, either use a pin that has the desired default pull direction, or override it with an external pull Dec 25 14:55:18 thanks zmatt for your response ! Dec 25 14:56:08 oh! Dec 25 14:56:26 there's another potential issue: u-boot might be doing some bogus pin configuration Dec 25 14:56:35 I don't know if that's been fixed yet Dec 25 14:56:38 I have >20 BBAIs and the particular pin state is different in them Dec 25 14:57:36 that's why I couldn't find the generic solution !! Dec 25 14:58:01 if the pin level is being driven (rather than being weakly pulled) or pulled in a direction other than the reset default one, then u-boot is to blame Dec 25 14:58:34 that's what I'm doubting.. Dec 25 14:59:08 officially TI actually expects pin configuration to be done in u-boot for this SoC rather than in dts (see AM572x erratum i896) Dec 25 14:59:38 I'm loading same image to all 20 BBAIs (by using memory card) still u-boot is to blame ? Dec 25 14:59:42 unfortunately the BBAI shipped with an u-boot that performed pin configuration intended for the AM572x EVM Dec 25 14:59:56 are you reflashing eMMC ? Dec 25 15:00:03 yes ! Dec 25 15:00:08 oh, huh Dec 25 15:00:31 I'm out of clue how to explain this behavior. Dec 25 15:01:56 I can tell you the exact pin P8.17. In .DTS I configured it to internal Pull Down. Still some BBAI shows high value initially (till 8-9s) and later comes to Low Dec 25 15:02:34 zmatt.. please Guide me the way Dec 25 15:02:51 that pin should definitely have internal pull-down by default Dec 25 15:04:04 earlier it was floating around 1.2Vcan you share me your mail so I can share you the dts file Dec 25 15:04:30 1.2V is neither high nor low Dec 25 15:04:47 It'll be curfew in half an hour and I got to go home :( Dec 25 15:05:21 I need to go for a bit myself Dec 25 15:05:39 Boss needs an explanation and I can't justify same product, same OS, different behavior of PIN Dec 25 15:05:58 yeah, do come back here! this is a good question and it needs to be resolved Dec 25 15:06:30 Sure.. after 14 hours I'll be back Dec 25 15:06:33 the whole pin configuration mess on the BBAI is still work-in-progress and I don't actually know the current state of it Dec 25 15:06:57 Do you want to know anything regarding this problem Dec 25 15:07:43 I'm still inclined to blame bogus pin configuration being done in u-bot Dec 25 15:07:46 *u-boot Dec 25 15:08:10 though I don't know why it's resulting in inconsistent levels for you Dec 25 15:08:14 I succeeded pin config by dts , enabled I2C, UARTS all working fine.. But before booting sequence LED starts this irregular behavior irritates me Dec 25 15:09:01 ok catch you tomorrow Dec 25 15:09:10 later! Dec 25 15:09:47 do let me know where can I report this problem.. and get feedback I hardly do community :( **** ENDING LOGGING AT Sat Dec 26 03:00:13 2020