• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 2094 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/BEAGLEBOARD-X15: Getting Started with the X15

Madhusudan Sampath52
Prodigy 20 points
Part Number: BEAGLEBOARD-X15
Other Parts Discussed in Thread: AM5728,

Tool/software: Linux

Hi!

I've recently gotten a BeagleBoard X-15 with the AM5728 mounted on it for some application development in-house, within TI. I'm facing some fairly fundamental issues that are preventing me from proceeding. It would be great if you could point me to the right resources/let me know how I can resolve the same: I'm also not too familiar with Linux, so any material on that front is also welcome!

  • Is there some kernel update of some sorts I need to do out of the box, or is the X15 ready to go as is? There's nothing mentioned at this link. If so, what are the steps to be followed?
  • I am not ale to use PuTTY to connect to the X-15 as mentioned in the link above, either. This is not a concern for me since my application doesn't demand it, but I'm not sure if that's indicative of something else.
  • How do I connect to the internal TI network? I tried adding proxies in the ~/.bashrc file and sourcing the same, but am not able to get the BeagleBoard through the firewall.
  • As an extension of the above, I'm not able to edit the /etc/apt/apt.conf.d/70debconf file to configure apt-get for package download, as mentioned in this link. I do not know the root/user password for the device to su or sudo.

Please help me with the above. I understand that not all questions may be answered here, since this is an external forum - please feel free to mail me.

Thanks!

Madhu

  • 0
    TI__Guru**** 161600 points
    Hi,

    From the description of your linux, I guess you use the community release (Debian), right? Debian is supported by Beaglebone community.

    Try using Processor SDK Linux:
    software-dl.ti.com/.../index_FDS.html

    It should be usable with BeagleBoard X15, though I've not tested this myself.

    Then the Software Developers User Guide for Processor SDK RTOS is here:
    software-dl.ti.com/.../index.html

    Best Regards,
    Yordan
  • 0
    TI__Prodigy 10 points

    I followed the instructions in the Getting Started guide to make sure I was running the latest Debian image:

    http://beagleboard.org/getting-started

    Latest image is here.  Make sure you choose the link for Beagleboard-x15, not BeagleBone as shown below.

    https://beagleboard.org/latest-images

    https://debian.beagleboard.org/images/bbx15-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz

    I then used the Etcher program from the Getting Started guide to put that image onto an sd card and used that to boot the BeagleBoard-x15.

    Doing a 'cat /proc/version' reports the following:

    Linux version 4.14.71-ti-r80 (root@b2-am57xx-beagle-x15-2gb) (gcc version 5.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 2018

    To update the new image onto the eMMC, do the following:

    To turn these images into eMMC flasher images, edit the /boot/uEnv.txt file on the Linux partition on the microSD card and remove the '#' on the line with 'cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh'. Enabling this will cause booting the microSD card to flash the eMMC. Images are no longer provided here for this to avoid people accidentally overwriting their eMMC flash.

    Etcher only creates a file system large enough to hold the image. To maximize the size of the file system on the sd card I did the following:

    cd /opt/scripts/tools/

    git pull || true

    sudo ./grow_partition.sh

    sudo reboot

    I hope this helps!

  • 0
    TI__Prodigy 20 points

    Thanks for the suggestions, Yordan and Yazdi!

    I will get the kernel up to speed with Yazdi's instructions - I think I will stick to Debian for the time being. 

    • Internet issues were fixed with a change in the proxy settings, and by launching Chromium from the command line instead of from the GUI.
    • The user password for Debian was found to be documented online, here.

    I have not yet fixed the PuTTY issues, I will try and update when I do so. 

    Madhu