This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM335x EVM-SK: touchscreen is not working

Hi all,

I have a problem, so I need your advice. I bought the kit AM335x EVM-SK and I configure my host PC which has Ubuntu 12.04 LTS 64 bit. While running setup.sh, the touchscreen stop working and after that time, it is not working for my linux micro SD card. However, it is working when I insert Android micro SD card. In addition to that, when I try to connect my board with minicom, It is not responding and the terminal program gives the output shown below

Retry count exceeded; starting again 
link up on port 0, speed 100, full duplex 
BOOTP broadcast 1 
*** Unhandled DHCP Option in OFFER/ACK: 46 
BOOTP broadcast 2 
BOOTP broadcast 3 
BOOTP broadcast 4 
BOOTP broadcast 5 
BOOTP broadcast 6 
BOOTP broadcast 7 
BOOTP broadcast 8 
BOOTP broadcast 9 
BOOTP broadcast 10 

Retry count exceeded; starting again 
link up on port 0, speed 100, full duplex 
BOOTP broadcast 1 
*** Unhandled DHCP Option in OFFER/ACK: 46 
BOOTP broadcast 2 
BOOTP broadcast 3 
BOOTP broadcast 4 
BOOTP broadcast 5

When I insert my linux microsd card to my host pc via adapter, my host pc can't see the microsd card. I would like to ask what I should do to solve this problem. I applied the things given below but my situation is still the same.

http://e2e.ti.com/support/arm/sitara_arm/f/791/p/209047/827659.aspx

Thanks in advance.

  • Hi,

    Did you try using the create-sdcard.sh script to create a new SD card? Perhaps something went wrong to this one.

    The create-sdcard.sh script is located in <sdk_folder>/bin/

    Best regards,
    Miroslav

  • Thank you for your reply Miroslav,

    I run the create-sdcard.sh and the output on the terminal is

    ege@ege:~/ti-sdk-am335x-evm-06.00.00.00/bin$ sudo ./create-sdcard.sh


    ################################################################################

    This script will create a bootable SD card from custom or pre-built binaries.

    The script must be run with root permissions and from the bin directory of
    the SDK

    Example:
     $ sudo ./create-sdcard.sh

    Formatting can be skipped if the SD card is already formatted and
    partitioned properly.

    ################################################################################


    Availible Drives to write images to:

    #  major   minor    size   name
    1:   8       16    3872256 sdb
     
    Enter Device Number or n to exit: 1
     
    sdb was selected

    SD Card is not correctly partitioned

    ################################################################################

        Select 2 partitions if only need boot and rootfs (most users)
        Select 3 partitions if need SDK & CCS on SD card.  This is usually used
            by device manufacturers with access to partition tarballs.

        ****WARNING**** continuing will erase all data on sdb

    ################################################################################

    Number of partitions needed [2/3] : 2

     
    Now partitioning sdb with 2 partitions...
     

    ################################################################################

            Now making 2 partitions

    ################################################################################

    dd: writing `/dev/sdb': Input/output error
    1+0 records in
    0+0 records out
    0 bytes (0 B) copied, 0.0021029 s, 0.0 kB/s
    DISK SIZE - bytes
    (standard_in) 1: syntax error

    Usage:
     sfdisk [options] <device> [...]

    Options:
     -s, --show-size           list size of a partition
     -c, --id                  change or print partition Id
         --change-id           change Id
         --print-id            print Id
     -l, --list                list partitions of each device
     -d, --dump                idem, but in a format suitable for later input
     -i, --increment           number cylinders etc. from 1 instead of from 0
     -u, --unit <letter>       units to be used; <letter> can be one of
                                 S (sectors), C (cylinders), B (blocks), or M (MB)
     -1, --one-only            reserved option that does nothing currently
     -T, --list-types          list the known partition types
     -D, --DOS                 for DOS-compatibility: waste a little space
     -E, --DOS-extended        DOS extended partition compatibility
     -R, --re-read             make the kernel reread the partition table
     -N <number>               change only the partition with this <number>
     -n                        do not actually write to disk
     -O <file>                 save the sectors that will be overwritten to <file>
     -I <file>                 restore sectors from <file>
     -V, --verify              check that the listed partitions are reasonable
     -v, --version             display version information and exit
     -h, --help                display this help text and exit

    Dangerous options:
     -f, --force               disable all consistency checking
         --no-reread           do not check whether the partition is in use
     -q, --quiet               suppress warning messages
     -L, --Linux               do not complain about things irrelevant for Linux
     -g, --show-geometry       print the kernel's idea of the geometry
     -G, --show-pt-geometry    print geometry guessed from the partition table
     -A, --activate[=<device>] activate bootable flag
     -U, --unhide[=<dev>]      set partition unhidden
     -x, --show-extended       also list extended partitions in the output,
                                 or expect descriptors for them in the input
         --leave-last          do not allocate the last cylinder
         --IBM                 same as --leave-last
         --in-order            partitions are in order
         --not-in-order        partitions are not in order
         --inside-outer        all logicals inside outermost extended
         --not-inside-outer    not all logicals inside outermost extended
         --nested              every partition is disjoint from all others
         --chained             like nested, but extended partitions may lie outside
         --onesector           partitions are mutually disjoint

    Override the detected geometry using:
     -C, --cylinders <number>  set the number of cylinders to use
     -H, --heads <number>      set the number of heads to use
     -S, --sectors <number>    set the number of sectors to use


    ################################################################################

            Partitioning Boot

    ################################################################################
    mkfs.vfat 3.0.12 (29 Oct 2011)
    /dev/sdb1: No such file or directory

    ################################################################################

            Partitioning rootfs

    ################################################################################
    mke2fs 1.42 (29-Nov-2011)
    Could not stat /dev/sdb2 --- No such file or directory

    The device apparently does not exist; did you specify it correctly?


    ################################################################################

       Partitioning is now done
       Continue to install filesystem or select 'n' to safe exit

       **Warning** Continuing will erase files any files in the partitions

    ################################################################################


    Would you like to continue? [y/n] : y

     
     
    Mount the partitions
    mount: special device /dev/sdb1 does not exist
    mount: special device /dev/sdb2 does not exist
     
    Emptying partitions
     

    Syncing....

    ################################################################################

        Choose file path to install from

        1 ) Install pre-built images from SDK
        2 ) Enter in custom boot and rootfs file paths

    ################################################################################

    Choose now [1/2] : 1

     
    Will now install from SDK pre-built images
    now installing:  ti-sdk-am335x-evm-06.00.00.00
    ################################################################################

        Copying files now... will take minutes

    ################################################################################

    Copying boot partition

    MLO copied


    u-boot.img copied

    uImage copied

    Copying rootfs System partition
    Written 100%  

    Syncing...
     
    Un-mount the partitions
    umount2: Invalid argument
    umount: boot: not mounted
    umount2: Invalid argument
    umount: rootfs: not mounted
     
    Remove created temp directories
     
    Operation Finished
     
    ege@ege:~/ti-sdk-am335x-evm-06.00.00.00/bin$

    After this operation, when I insert my microsd card to my starter kit, touchscreen still is not working.

  • Hi,

    Try a new SD card. Judging by the "dd" operation error output, your SD card may have a hardware issue.

    Best regards,
    Miroslav

    P.S. Please, when posting logs to the forum, attach them as a log file, so that the post is clean and easily readable.

  • I've had formatting errors on micro sd cards before.  You may want to check your SD adapter or make sure the card is inserted properly in your PC's SD slot.  You can also run Ubuntu's disk utility: System->Admin->Disk Utility.  Click on the sd partition and run an error check. 

    Sometimes, the sd create script will fail to reformat the card, but with Ubuntu's disk utility, you may be able to delete the partitions and reformat the card.  Then try the create script again.  I have been able to 'restore' some sd cards this way. 

    However, an engineer's time is valuable, so you'll have to decide whether it is worth trying to keep restoring a possibly defective card or buying new ones.  I've tried class 4 thru class 10 cards, kingston brand with a noticeable difference in speed with class 10s but no difference in reliabilty, ie, equal 'corruption' rates for each class.

  • Thank you for your answers.

    @Miroslav: I will buy another micro SD card, if I can't solve the problem with the method argeebee suggest. Thank you for your interest.

    @argeebee: I opened the disk utility and I choose the mass storage device but unfortunately there is no option with error check.  When I choose my local hard disk, I have the option with check filesystem but for the mass storage device I have no option with this. I am sending the printscreen of my disk utility. When I select format drive, the system faced with error. What should I do to restore the disk? By the way, thank you for your interest.  

    Best regards,

    Ege

  • "When I select format drive, the system faced with error."

    Even a fresh blank card out of the box should allow a format.  The capacity of your card can be obtained, so its controller may be working.  Check the lock tab on the SD adaptor and make sure it is not locked.  Also, to make sure the adaptor is ok, try another SD card and see if the disk utility can see it.

    You can only do an error check on a formatted partition.  I suggested an error check after a format to verify that the format could write the card properly.  If you can't recover the card, a new card is relatively cheap.  Another alternative is to boot via NFS, but that can be difficult on the SK's usb/serial port.