• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 629 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.

Cannot boot into c6x on 6678 EVM

M S1
Prodigy 170 points

I followed the instructions in the Linux c6x User's Guide to build c6x for the 6678 EVM.

Using the Linux version of CCS and program_evm, I pretty much bricked the EVM.  No POST, no Linux, no TFTP, etc.

I switched over to the Windows versions of CCS and program_evm, and I can now run POST.  I also get a little further with c6x, in that the serial output says "IBL: Booting from NAND", which it repeats, but never actually boots c6x.

I'll also chime in with other posters on the forum about the lack of clear documentation from TI on how to do something pretty basic.

I think the problem must be in my build process.  I've followed all the steps "prj config", "prj build" etc., and I've copied over different bin files that I renamed "nand.bin", including evmc6678-initramfs-demo*.bin, evmc6678-initramfs-min*.bin, etc.

Is there any troubleshooting advice, or does anyone have a c6x bin file I can download, just to verify if I have a build issue?  When the EVM was delivered to me by my customer, it would boot into c6x.  I added some functionality and rebuilt, but have never been able to boot a c6x that I have built.

Would it be worth trying to load the vmlinux build from CCS as an alternative?

Thanks,

MS

  • 0
    TI__Guru 50170 points

    Hi, MS,

    There are pre-build images in linux-c6x release package under program_evm directory. Please give it a try. You can also try using CCS to load the pre-build vmlinux.bin file to the memory address at 0x80000000 and set the IP to 0x80001000 and click resume. If you use the vmlinux ELF file you build, use load program instead load memory in previous case and resume. If you don't have a Mezzanine Jtag emulator, using CCS may have an issue because the USB is shared with UART and only one is active based on jumper setting. Using JTAG will lose UART.

    Rex

  • 0 in reply to Rex Chang
    Prodigy 170 points

    Hi Rex,

    The problem is the nand.bin file is not supplied.  From page 1 of the program_evm user guide:

    The following files are the factory default images under
    program_evm\binaries\evm6678l.


    Note: Please note that nand.bin and nand_oob.bin are not supplied from BIOS
    MCSDK releases. Please refer to the DVD shipped along with the EVM for
    nand.bin file

    There is no "nand.bin" file anywhere on any DVD, at least that I can find.  Am I missing something, but it seems like you must build c6x in order to get a nand.bin file.

    Thanks, ms

  • 0 in reply to M S1
    TI__Guru 50170 points

    Hi, MS,

    You mentioned that you copied over the bin file and renamed it to nand.bin. Where did you copy it to? to program_evm/binaries/evmc6678l? In the released package, just create a symbolic link to the bin file in that directory. When you run .js script file, provide nand as image identifier.

    Rex

  • 0 in reply to Rex Chang
    Prodigy 170 points

    Hi Rex,

    I've tried it both ways, renaming the file and creating a symbolic link, with the same results. I've also tried it in both Linux and Windows.

    In Windows, I set the DSS_SCRIPT_DIR and PROGRAM_EVM_TARGET_CONFIG_FILE environment variables, and use the following command:

    %DSS_SCRIPT_DIR%\dss.bat program_evm.js TMDKEVM6678L-le nand

    In Linux I export the environment variables, and use this command:

    $DSS_SCRIPT_DIR/dss.sh ./program_evm.js evm6678l-le "nand"

    In both operating systems the flash completes without error, but when booting I just see the "IBL: Booting from NAND" message then the board hangs.

    Thanks, ms

  • 0 in reply to M S1
    TI__Guru 50170 points

    Hi, MS,

    I did it in Linux which still needs to export TARGET_CONFIG_FILE. I captured what I did for programming the NAND and attached the minicom output at the end of the file. It takes about 20-30 secs for kernel to boot.

    Rex

    8078.c6678_nand_boot.txt

  • 0 in reply to Rex Chang
    Prodigy 170 points

    Rex,

    I think we're getting somewhere now.  When I run bootblob get-cmdline, this is what I see:

    console=ttyS0,115200 rw mem=256M ip=dhcp  initrd=0x80500000,0x300000

    The second parameter of my initrd is 0x300000, while yours is 0x500000.  Could this be the root of my issue?

    Thanks, ms

  • 0 in reply to M S1
    TI__Guru 50170 points

    Hi, MS,

    Is this bin file you built? I have several bin files which shows different sizes. I suggest that you change one variable at a time and start with pre-build image. Once the pre-build image can boot successfully, then we work on the build issue if your image still does not boot after that.

    Rex