This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DS-5 Android - Problem debugging on a device

Note: This was originally posted on 19th April 2012 at http://forums.arm.com

I've finally managed to make the emulator work and now can debug my game on it. Thank you.

As I don't have an actual android device, I've installed an experimental version of ICS on my HP TouchPad. It seams everything works all right. I can use the adb utility provided with the SDK to connect to the device with no problem. But I cannot debug from inside eclipse under windows on the actual device.

I created a second debug configuration for the device and selected my device in the Connection tab at the combo-box, but after a while I receive a message that eclipse cannot connect to the device. This is strange as I have no problem with the connection. Under a dos window using the adb command I can see I can connect, I even can shell into the device.
Parents
  • Note: This was originally posted on 25th April 2012 at http://forums.arm.com


    I've finally managed to make the emulator work and now can debug my game on it. Thank you.

    As I don't have an actual android device, I've installed an experimental version of ICS on my HP TouchPad. It seams everything works all right. I can use the adb utility provided with the SDK to connect to the device with no problem. But I cannot debug from inside eclipse under windows on the actual device.

    I created a second debug configuration for the device and selected my device in the Connection tab at the combo-box, but after a while I receive a message that eclipse cannot connect to the device. This is strange as I have no problem with the connection. Under a dos window using the adb command I can see I can connect, I even can shell into the device.


    Hi,

    Ok, so carrying on from where we left the discussion on http://blogs.arm.com...nts__1__st__15/ , you could search for a file called adb_common.py inside your configdb directory. The error message that you see ( "Error encountered when communicating... ) is coming from this file, from a function named adb_check(). So it looks like the sanity check for the adb connection is failing. This could be due to several reasons, I'll pass this on to the development team and see if I get any answers.

    Vinod
Reply
  • Note: This was originally posted on 25th April 2012 at http://forums.arm.com


    I've finally managed to make the emulator work and now can debug my game on it. Thank you.

    As I don't have an actual android device, I've installed an experimental version of ICS on my HP TouchPad. It seams everything works all right. I can use the adb utility provided with the SDK to connect to the device with no problem. But I cannot debug from inside eclipse under windows on the actual device.

    I created a second debug configuration for the device and selected my device in the Connection tab at the combo-box, but after a while I receive a message that eclipse cannot connect to the device. This is strange as I have no problem with the connection. Under a dos window using the adb command I can see I can connect, I even can shell into the device.


    Hi,

    Ok, so carrying on from where we left the discussion on http://blogs.arm.com...nts__1__st__15/ , you could search for a file called adb_common.py inside your configdb directory. The error message that you see ( "Error encountered when communicating... ) is coming from this file, from a function named adb_check(). So it looks like the sanity check for the adb connection is failing. This could be due to several reasons, I'll pass this on to the development team and see if I get any answers.

    Vinod
Children
No data