• Not Answered

ADB on TAM3517 TwisterBoard

Hi all,

sry for asking on answered post...

Can you tell me how to get ADB-connection to TAM3517 on Twisterboard???

Cause if I check for devices with command "adb devices" I always get an empty list....

A few things to check:

- is adb platform support added to your board file?
- is adb enabled in your kernel build?
- do you see adb_init or similar logs in kernel boot log?
- do you see any logs when you attach or detach the adb usb cable?

Please start a new topic the next time and not hijack an existing thread.

sry again for hijacked another post...

board file and kernel build I wasn't able to check until now cause we're using a precompiled Image from TechNexion here... but we're looking for getting the sources

on boot log the are the lines :

"f_adb init

android_register_function adb"

no reaction on the logs when I attach or detach the cable, only the OTG-port getting current-supply over USB... 

perhaps you also know a better way for what I wanna do?

I want to use "chmod" over adb for using the serial_port_api on the device, but therefor I need read/write-permission for my App on the /dev/ttyS* nodes... 

So wether I use chmod to do it with userrights or to root my device, but I think for both procedures I need ADB?

6 Replies

  • Christian Richter

    I want to use "chmod" over adb for using the serial_port_api on the device, but therefor I need read/write-permission for my App on the /dev/ttyS* nodes... 

    If you are using TI Android DevKit, you can modify your init.rc in the SD card directly or chmod from the debug serial console if adb is not working.

  • In reply to Vishveshwar Bhat:

    thanks Vishveshwar,

    but how can I use debug serial console, I know I can sniff debug messages by a serial monitor, but not how to get in the console...

    I want to test changing the init.rc at another EVM (AM3517EVM) where adb is no problem and I can look at the permission of devices...

    But after adding the line "chmod 0777 /dev/ttyO2" at the end of init.rc an restart the device, it don't worked

    So what's wrong here?

    BR,

    Christian

  • In reply to Christian Richter:

    Christian Richter

    But after adding the line "chmod 0777 /dev/ttyO2" at the end of init.rc an restart the device, it don't worked

    Please add your 'chmod XXX '  lines after the 'chmod XXX' entries already present in init.rc.

    init.rc is composed of many sections and adding this line in the wrong section may not have any effect or may break something else.

    Also please note that /dev/ttyO2 is currently used on AM35x evm for debug serial and may be not used by other apps. If you wish to use the same port, then you need to modify the bootargs to stop using /dev/ttyO2 for debug serial.

  • In reply to Vishveshwar Bhat:

    Thanks Vishveshwar,

    worked on AM3517EVM, but now back to Twisterboard TAM3517...

    If I change init.rc the same way there it only works on booting from SD-card, but when we're playing the image to and booting from NAND Flash, he ignores the changes to init.rc again... 

    So is there a possibility to change the permissions on NAND Flash, too?

    How does commanding with serial console work, is there a UserGuide or something like that?

    Does anyone know if Twisterboard should support ADB over Ethternet? I only tried over USB until now...

    BR,

    Christian

  • In reply to Christian Richter:

    Christian Richter

    If I change init.rc the same way there it only works on booting from SD-card, but when we're playing the image to and booting from NAND Flash, he ignores the changes to init.rc again... 

    So is there a possibility to change the permissions on NAND Flash, too?

    Make sure that the modified init.rc is written back to the flash. Generally, when booting from flash, rootfs is mounted as read-only. You may have to remount with read-write permissions.

  • In reply to Vishveshwar Bhat:

    Vishveshwar Bhat
    Make sure that the modified init.rc is written back to the flash. Generally, when booting from flash, rootfs is mounted as read-only. You may have to remount with read-write permissions.

    How can I verify that without root-permissions??

    BR,

    Christian