Raspberry Pi or Beaglebone device debugging

Hi,
Im not sure about states on the bug status and have no dates. Theres any progress on this problem?

Best regards.

This (all except the crash with the Connect to CrossBox dialog) should be fixed in the build that came out after we last talked (ie 2-3 weeks ago).

bugs://82804 got closed with status fixed.

And thats the issue for registering a server from Fire, fixed.

1 Like

Thanks, will test when come back to Panama (Im in Honduras right now)

Best regards.

1 Like

Testing Island project (Linux) to ubuntu 18.04 cant debug.

Says disconnected but it validates ok and the server is online (im connected via ssh same credentials)

When try to run project get that

That’s ok.expected Fire does not make a live connection to the server itself (like Water does), but the debugger should still be able to connect as needed (which it tries to do, but fails with the error message form your second screenshot:

This looks like you have neither a password nor a key file specified for the server. What does your CrossBox.xml file look like (X out the password before posting, if you have one in there), and do you have an ~/.ssh.id_rsa key file on your client system?

Im using user/password combination, no keyfile. To validate the server you must input user and password. The data was there.

Have no idea where is located. Can please tell me where to look up?

Hmm, the error you showed would only happen if neither password nor keyhole were specified…

~/Library/Application Support/RemObjects Software/Elements/CrossBox.xml

The file name seems to be different

hasPassword=true, thats good. the password itself should be stored in the key chain, can you see if ts there, if you search by the username?

In which path?

in KeyChain.app. eg:

if Donald was your user name.

the hidden field have user@server

odd. and when you check show password, is the password correct?

if so, this should work, I guess is;'ll have to debug this on Monday. by first finding a server that uses passwords l;). as workaround, can you try to use keys? much securer, anyways…

Yes, the password is correct.

Im using a private point to point VPN, for that reason the security is more relaxed. Have no idea how to use keys. If you can give me directions I can try.

Bets regards.

Check out https://docs.elementscompiler.com/Tools/CrossBox/CrossBox2/SettingUp/.

Will try, thanks

BTW the documentation have a little error

ld ~/.ssh must say ls ~/.ssh

bets regards

Now I have ssh connecting without ask for a password. Good.

What im doing wrong?

BTW, I suggest also you add to the tuto this info

to send the private key to the target computer

ssh-copy-id your_username@192.0.2.0

ive had this too. not seems that some SSH implementations dont like “-----BEGIN OPENSSH PRIVATE KEY-----” keys, only “-----BEGIN RSA PRIVATE KEY-----”. It depends omg the system where you generate they key, apparently. Check your key file; I’m not sure if simply changing there string from OPENSSH to RSA suffices, or if its actually a different format…

I’ll fix the types/issues in the tutorial.