• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 162 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.

Flashing Custom Kernel with SDK 5.04

Kevin Cutts
Prodigy 50 points

So I found the directions to use create-sdcard.sh to create a bootable SD card (working on a beagle-xm). And that works with the provided images. But when I try to install a custom kernel (the one I built), it asks for the directory of the source. What do I use?I suspected I should use the "stuff" in the targetnfs directory but that is a single directory...

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

  For Boot partition

  If files are located in Tarball write complete path including the file name.
      e.x. $:  /home/user/MyCustomTars/boot.tar.gz

  If files are located in a directory write the directory path
      e.x. $: /ti-sdk/board-support/prebuilt-images/

  and the beginning of the files should be labeled with MLO, u-boot, uImage
      i.e.   test_MLO_image must be labeled as MLO_test_image

  NOTE: Not all platforms will have an MLO file and this file can
        be ignored for platforms that do not support an MLO
################################################################################

Enter path for Boot Partition :

  • 0
    TI__Guru*** 125430 points

    Kevin,

    I split the thread for these reasons.

    The SD card that you're creating will have two partitions: boot and rootfs.  You correspondingly need 2 directories/tarballs.  You could make your own directory "my-images" and put your own MLO, u-boot.img, and uImage into that directory.  Then point the script to that directory and your binaries will be written to the SD card instead of the prebuilt binaries.

    Brad