reset the Beaglebone Black

This topic has 15 replies, 2 voices, and was last updated 4 years ago by harrison.

Viewing 15 posts - 1 through 15 (of 16 total)

1 2 →

Author

Posts
September 25, 2020 at 5:30 pm #969

pablo
Participant

Hello, we had an issue installing Linux into the Beaglebone Black (step 1.3 in the software guide). The installation was not working and we didn´t know why, so decided to press the reset button in order to follow the tutorial from scratch. The problem is that the reset apparently changed the files of the Beaglebone Black, so what should we do to solve it and be able to install Linux from the micro sd? Thanks in advance for your help!

September 25, 2020 at 8:52 pm #970

pablo
Participant

Just for more information about the issue. When trying to flash Linux into the Beaglebone Black, only LED 1 and slightly 3 were lighting (instead of the 4 of them). So that’s why we thought something was wrong and after 40 min (it is supposed to take 15 min) we pressed the reset button of the Beaglebone. After that, when we connect to the computer without the micro sd card, the 4 LEDs turn on at the same time and it is not recognized by the computer. When we connect it with the flashed micro sd and press button S2, then we go back to the same state of LED 1 and slightly LED 3 lighting and at that moment it is recognized by the computer. Do you know how to solve the issue and which should be exactly the light pattern while flashing Linux into the Beaglebone? Thanks!

September 26, 2020 at 8:59 am #971

harrison
Keymaster

Hi Pablo,

When flashing correctly the lights should oscillate back and forward if I recall correctly. It should be obvious if it is working; it will only take 15 minutes then the device will reset itself. I think you are correct that yours did not work.

Did you:
1) Go into the Beaglebone and make the changes described in the “flashing eMMC” section on this page: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC
2) Hold the S2 switch when you turn it on with the SD card (set up for flashing) installed?

If you didnt do either of these that is a likely cause – potentially number 1 could be the primary issue.

When you say the setup “changed the files” on the Beaglebone does this mean you can no longer log into it using Putty?

I can try replicating the issue next week on one of my devices and see if there is any update or such that could be causing trouble.

September 26, 2020 at 10:51 am #972

pablo
Participant

HI Harrison,

Thanks a lot for your reply!

1) Yes, we changed the code as described
2) Yes, we hold S2 switch for 20 seconds when connecting the Beaglebone with the flashed micro sd to the computer

About the files I would have to check again with the device next week. The main issue is that now, after trying to flash Linux into the beaglebone and then reset it, when connecting the Beaglebone w/o micro sd to the computer it is not recognized and we cannot access it using Putty (here 4 lights are constantly on). If we connect it instead with the micro SD card in and hold the S2 button, then the computer recognizes it and we can access it with Putty (in this case light 1 will be flashing intermittently, and light 3 will flash weakly, lights 2 and 4 will be off)

If you need any more details to try to replicate the issue I can check anything from Monday as we have the beaglebone in the lab, just let me know. Thanks in advance for your help.

September 28, 2020 at 6:19 pm #973

pablo
Participant

Good news, THE ISSUE IS SOLVED. I don’t know which was the problem, I think I did the same as the first time. This time, however, as the beaglebone was only recognized by the computer with the card inside I access it through putty like that. Then I edited the code as described, disconnect, connect again and the Linux flashing worked!

Now, unfortunatelly I am STUCK IN A FURTHER STEP: when connecting the beaglebone to the internet through USB. We have a windows 10 pc, I followed the tutorial in http://ofitselfso.com/BeagleNotes/HowToConnectPocketBeagleToTheInternetViaUSB.php , everything worked and when runing <ping 8.8.8.8> it is working. The problem comes when we have to configure our nameserver. The file /etc/resolv.conf did not exist, so I created it a wrote in it the following as described:
domain localdomain
search localdomain
nameserver 8.8.8.8
nameserver 8.8.4.4
But after this, the command <ping google.com> still doesn´t run, it says “Temporary failure in name resolution”
Then I tried to connect to the beaglebone with FileZilla (using IP 192.168.7.2, port 22, password temppwdt, but they don´t ask for user) it does not work. It prints “Protocol error: Unknown protocol identifier (0x83 0x83 0x72) most likely connected to the wrong port. Connection to server closed”. I guess it can be due to the fact that I couldn´t configure my nameserver.

Could you give any advice to solve this problem? Thanks in advance for your help!

September 30, 2020 at 8:37 am #975

harrison
Keymaster

Hey Pablo,

Filezilla should be independent of the nameserver issue. When you open Filezilla it should look something like this: https://upload.wikimedia.org/wikipedia/commons/9/95/FileZilla_3.7.3.png
Along the top are the fields for host (192.168.7.2) username (debian) password(temppwd) and port (22). Does yours not show this?

Regarding the file /etc/resolv.conf, what _is_ in the directory /etc/? There should be several files there, it is surprising that this one would be missing – I have never seen such an error. If you navigate to the root directory and then enter /etc/ and run command “ls” what does it show in that folder?

In practice you shouldnt even need to do the editing of resolv.conf yourself – it is done automatically by our script setup.sh (i.e. here https://github.com/HarrisonSteel/ChiBio/blob/master/setup.sh). So, maybe focus on getting Filezilla to work, then it should sort it out itself when you run this script.

September 30, 2020 at 6:32 pm #976

pablo
Participant

Thanks a lot for your answer!

Regarding resolv.conf I actually can see the file inside /etc, the problem is that if I try to see its content for example with “less /etc/resolv.conf” it says that there is no such file or directory. Then I edit it with nano or vim, and now I can see the changes are saved, but still ping google.com wouldn´t work; then if I disconnect the beaglebone and connect again, the file resolv.conf will be empty again.

Anyway, as you suggest, I will focus on the FileZilla problem, because in my case it does not look like the image you sent, so I´ll try to download the right one and see if I continue the tutorial from there and run the setup.sh

October 1, 2020 at 2:15 pm #985

pablo
Participant

Hello, we managed to connect through FileZilla and run the setup.sh, however, I think it didn´t work properly.

After running it we could register through putty using root as user and password as described; then inside /root/chibio we have the following 4 files: “app.py”, “cb.ch”, “static”, “templates”. However, the reason why I think it didn´t work is that we got all the following errors while running the setup.sh (they will be separated in different messages because otherwise it doesn´t let me comment, I guess the reason is that it is too long):

October 1, 2020 at 2:32 pm #993

pablo
Participant

(CONTINUE MESSAGE 985)
Sorry it doesn´t let me copy the code, hope this link works: https://docs.google.com/document/d/1C4R39JM59ymFWdwxof-KUE9ZMRZZUpRRx6GNE0lL2sA/edit?usp=sharing

Does anyone know which can be the problem (or is it possible that those are minor errors) ? I guess we still have a problem with the connection, but I don´t know how to solve it. Any help is welcome. thanks in advance for your help!

October 5, 2020 at 2:05 pm #994

harrison
Keymaster

Hi Pablo,
From the file you attached it looks like the issues stem back to this issue with the nameserver.
I have heard of several others having issues in the past whereby they could not get the internet on the Beaglebone to work due to firewalls on their internet connection blocking access from the Beaglebone.

Are you able to connect via a different network? For instance, share internet from a phone to your PC, then connect through that to the internet? That way it would ideally bypass any institutional firewall you have that might be obstructing.
I will try replicating your error later today on one of my devices, and will try to see whether when I flash the system it has the correct resolv.conf in there.

Could you confirm to me what the complete filename of the operating system image you downloaded from this site was? https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_10_.28Buster.29_-_Weekly

October 5, 2020 at 2:34 pm #997

pablo
Participant

Thanks a lot for your answer. This is the operating system image I used: bone-debian-10.4-iot-armhf-2020-05-18-4gb.img, hope it is the correct one.

And about the connection, I can try to hotspot from a phone for example yes. Actually, I already read about that in the blog and tried that when I was having trouble with naming the network in the resolv.conf file (in this case, even with the hotspot connection I couldn´t manage to properly rename the network and get to work “ping google.com”, but maybe it helps to download the files properly when running setup.sh)

October 6, 2020 at 2:01 pm #998

harrison
Keymaster

I see, it looks like you may have downloaded the incorrect OS image. It should be the one named “bone-eMMC-flasher-debian-10.4-lxqt-armhf-2020-05-18-4gb.img.xz” which is in the row labelled “eMMC Flasher” on the site here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_10_.28Buster.29_-_Weekly.
It is directly below a different file (labelled microSD), which looks like what you have been using. So, if you change to the eMMC flasher file then I hope it will work straight away!

Harrison

October 6, 2020 at 2:57 pm #999

pablo
Participant

Oh shit! then yes, that might have been the problem (I´m so sorry for the confusion, and for the inconvenience), thanks a lot! I will try to repeat everything with the proper one and let you know if that works.

October 8, 2020 at 9:52 am #1005

pablo
Participant

Hello! I installed the proper Linux version and repeated everything. The internet connection was still failing but hotspotting from my phone solved it (so probably there are some issues with the university network). Now, when running setup.sh , packages can be download properly (I think), but after a bit less than 10 minutes I get an error and the beaglebone gets disconnected (I have tried several times and it always fails in the same step). There is an error about not enough space for cache at some point, but I am not sure if that is the problem. Here is the error I get (it is the second time I run it, so for that reason, some requirements are already satisfied): https://docs.google.com/document/d/1VNSd71KDLOIvlW6t1f4Hj9ExwGy09r3JkIv71Z1lbkI/edit?usp=sharing

Any help is appreciated. Thanks a lot!

October 13, 2020 at 7:31 pm #1011

pablo
Participant

Hello!Just as an update to my last comment. I also got an error with the pip command (you can see the error comment attached in the previous comment). I tried to install the “pip” command doing:
apt-get update
apt-get install python-pip
This produces the same error that I´m getting at some point when running setup sh: “E: You don’t have enough free space in /var/cache/apt/archives/”
I am wondering why I don´t have space or whether I should put a micro sd to have more space or something (sorry it is my first time with a beaglebone, maybe some questions are too obvious). Thanks in advance for your help!
Author

Posts

Viewing 15 posts - 1 through 15 (of 16 total)

1 2 →

You must be logged in to reply to this topic.