• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 278 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.

Trouble porting EZSDK to custom Sitara board

Ivan Todorovic
Intellectual 730 points

Hello,

We have a custom board with TI Sitara on it. We have successful ported TI's Android Gingerbread to it, but we have trouble porting EZSDK Linux (the latest version, ezsdk_dm816x-evm_5_03_01_15_setuplinux).

EZSDK Linux installs fine and runs fine on DM8168 evaluation board (both prebuild binaries and fresh binaries rebuilt with CodeSourcery). However, when we apply all the changes to EZSDK's U-Boot source, which we made to Android's U-Boot in order to boot our board, the SD card won't boot at all (we get nothing on the terminal via serial connection). It's not the connection problem because we changed the port from ttyO2 to ttyO0 in bin/mksdboot.sh script.

The interesting thing is that, when we make a bootable SD card with that script, like described in previous case, but replace MLO and uboot.bin with the working ones from our Android port, U-Boot executes fine, loads the kernel image and hangs at "Starting kernel..." on our terminal.

We also tried interrupting U-Boot and manual image loading utilizing various commands from include/configs/ti8168_evm.h (fatload mmc, fatload rescan etc) and still nothing.

And U-Boot's MLO binary rebuilt with CodeSourcery is almost twice the size of prebuilt MLO which comes with EZSDK Linux. Is that bad?

  • 0
    Intellectual 730 points

    Forgot to mention this: EZSDK (including its U-Boot) builds using CodeSorcery, while Rowboat Android builds using its own toolchain. Might that be a cause of problems?

  • 0 in reply to Ivan Todorovic
    Intellectual 730 points

    Status update:

    We rebuilt both EZSDK's U-Boot and Kernel (with necessary source code modifications for our Sitara board) using TI's Android Gingerbread toolchain (as seen here, section "Compilation procedure"), and it boots both U-Boot and Kernel!

    For an experiment, we also tried the same procedure, but now pointing the path to CodeSourcery's bin folder (containing gcc, g++ etc) and using CROSS_COMPILE=arm-none-linux-gnueabi- switch instead of CROSS_COMPILE=arm-eabi-. This builds the images but again, U-Boot won't even load. The same happens if we use official make clean - make all - make install method described in DM816x EZ Software Developers Guide.

    So currently it's a mistery why:

    1. Out-of-the-box sources build and run on EVM using required CodeSourcery toolchain
    2. Modified sources build but won't boot if CodeSourcery is used
    3. Modified sources build and boot if Gingerbread's toolchain is used