Error when trying to connect to beagle bone
9 visualizzazioni (ultimi 30 giorni)
Mostra commenti meno recenti
I am getting a lot of errors when I try to make a beagle bone object. I there a problem with the connection or do I have to install a package to the beagle bone?
>> bbb =beaglebone
Warning: Cannot determine version number of the board.
> In beaglebone/getBoardRevision (line 1647)
In beaglebone (line 276)
Warning: Cannot read the board serial number.
> In beaglebone/getBoardSerialNumber (line 1658)
In beaglebone (line 278)
Warning: Error while calling message/getString:
> In beaglebone.internal.errorhandler
In beaglebone/recvResponse (line 1315)
In beaglebone/enableADC (line 965)
In beaglebone/getAvailablePeripherals (line 1534)
In beaglebone (line 289)
Unable to find message key 'ERRNO4294967295' in catalog
'beagleboneio:server'.
Error in beaglebone.internal.errorhandler
Error in beaglebone/recvResponse (line 1315)
err =
beaglebone.internal.errorhandler(errno);
Error in beaglebone/enableADC (line 965)
obj.recvResponse();
Error in beaglebone/getAvailablePeripherals (line 1534)
obj.enableADC;
Error in beaglebone (line 289)
obj = getAvailablePeripherals(obj);
Error using beaglebone/recvResponse (line 1316)
Error in beaglebone/enableADC (line 965)
obj.recvResponse();
Error in beaglebone/getAvailablePeripherals (line 1534)
obj.enableADC;
Error in beaglebone (line 289)
obj = getAvailablePeripherals(obj);
3 Commenti
Nat AK
il 4 Gen 2018
Were you able to resolve this error? I have the same issue. Using 2016b. Thanks!
Tomas Pospíchal
il 31 Gen 2019
Running Beaglebone Black on Debian Jessie 8.9. This error is probably caused by reposponse from Matlab server running on beaglebone hw
resp =
1×3 uint32 row vector
4294967295 23 0
If you do not call funcion enableADC, this error doesn't occur.
Quick fix if you do not need Analog to Digital conversion
-> comment out line 1534 (obj.enableADC) in beaglebone support package
in function:
obj = getAvailablePeripherals(obj);
on line:
1532 % Find available Analog input pins
1533 obj.AvailableAnalogPins = {obj.BoardInfo.ADC.Name};
1534 %obj.enableADC;
This is caused by change with 4.x kernel in system device tree for overlays currently enabled by the cape manager [1]
from:
/sys/devices/bone_capemgr.*/slots
to:
/sys/devices/platform/bone_capemgr/slots
If you need this functionality you should be able to enable it by sending commad to your beaglebone
Risposte (3)
Gaurav Ahuja
il 8 Giu 2017
Modificato: Walter Roberson
il 11 Lug 2017
If this is the first time you are connecting with the board please use the following
bbb = beaglebone(deviceaddress,username,password)
use `bbb = beaglebone` if you want to reconnect to the same hardware. Find more details on this and on the default `username` and `password` in the following documentation link:
generally `bbb = beaglebone` should work as it can use this information from the connection that was created during the setup process as well. But if somehow you skipped the 'setup hardware' by clicking 'setup later', this will not be possible.
i request you to try this once. If explicitly specifying the deviceaddress, username and password do not work for you, revert back with your observations.
0 Commenti
RoyL
il 11 Lug 2017
Modificato: Walter Roberson
il 7 Mag 2018
I got a different error for 2017a version to connect to bbb.
>> bbb = beaglebone('192.168.7.2','root', 'root')
Error using beaglebone (line 236)
Cannot establish an SSH connection to the board with device address "192.168.7.2", user name "root", password "root". Check if device
address, user name and password are correct.
I verified the ssh connection from command line and it's working so it's not the ssh issue.
3 Commenti
lukman zainudin
il 25 Set 2018
I verified the ssh connection from command line and it's working so it's not the ssh issue.
Can I know how to verified the ssh connection? I have same issue from above, cannot connect to beaglebone hardware.
John Winkler
il 27 Set 2018
I have had a similar issue and what I learned from the support team is that the OS image for Beagleboard Black stopped being supported by Mathworks beyond Debian image 8.7 back in 2015. This stopped me moving forward because I need Debian OS image 9.1 or later to get the signed drivers needed by Windows 10. The developer team was made aware of this issue but I am not aware of an estimated date for a new produce support release. I spent two hours on the phone with the support team trying out all of their suggestions. It ended up with the later Debian images not yet supported by Mathworks development team.
I was also told that a workaround for this is to download the Simulink Coder Support Package for Beaglebone Blue hardware, use the hardware settings for the Blue, but then connect to your Black. Hacking the Blue workflow to make the compiler shipped with the 9.x Debian image compile the files on the "target" not the "host". The you get to do some more work in Simulink..... To use the board specific blocks in Simulink you navigate to Model Configuration Parameters - Code Generation - Custom Code then under Include Directories add in the additional paths for C:\ProgramData\MATLAB\SupportPackages\R20xx\toolbox\target\supportpackages\arm_cortex_a\include and C:\ProgramData\MATLAB\SupportPackages\R20xx\toolbox\target\supportpackages\arm_cortex_a\src then under Source Files in the Model Configuration you add the your source files like MW_led.c that are in the src directory you just added. I hope you get to the Simulink stuff after you do the BBBlue support package.
Sachin Umbarkar
il 25 Giu 2019
Getting following error while connecting the beaglebone Black hardware with MATLAB R2107B. Requested for help.
>> beaglebone_black
Error using matlabshared.internal.ssh2client
Error connecting to SSH server at 192.168.7.2
Error in beaglebone_black (line 152)
obj.Ssh = matlabshared.internal.ssh2client(hostname, ...
0 Commenti
Vedere anche
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!