Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
9 years ago

Downloading ELF failed

What do I do if I have the error "Downloading ELF failed" in Nios II SBT?

I built a system in Qsys that had 0 errors, it compiled and I could load it to the board.

What is then the error in Nios II SBT when I can't load the ELF file?

I tried different run configuration but none of them works.

The processor doesn't seem to respond:


$ nios2-download -g system.elf Using cable "USB-Blaster ", device 1, instance 0x00
Pausing target processor: not responding.
Resetting and trying again: FAILED
Leaving target processor paused

18 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    The Nios II data master is suppose to be connected to AVMM Slave of the jtag uart. Same goes with the timer.

    You debug_reset_request in your Nios II should be connected to the reset of jtag uart. And disconnect it from the clk_in_reset and nios_ii_gen2_reset.

    Refer to this: http://www.alterawiki.com/uploads/4/45/hello_world_lab_manual_max10.pdf and connect the debug_reset_request of nios ii to the jtag_uart_reset.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    I'm gonna check it.

    but you still have to check.

    is your clock(clk_0) working?

    is you reset_n signal pulled high?

    you need to check.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    Checkout this video and let us know if this helps ... it covers several ways to debug Nios+bare metal systems

    https://www.youtube.com/watch?v=tkvykoowbfe&t=57s&index=40&list=pl0pu5hg9ynizn8vpd1jrnwk6dlauccmdr

    --- Quote End ---

    Nothing helps. The problem is the debugging. If I get "Downloading ELF failed" then the problem could be anything. That is not a good debugging technique that some specific error could have any cause.

    I'm just trying to run a basic C program with the most simple design but no.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    you have to check those.

    1) reset_n

    do you give reset signal to nios?

    at least you need to give signal which stuck high.

    or a pulse it becomes low once is better.

    2)JTAG uart.

    if your Qsys does not have JTAG uart.

    you have no way to connect with your Qsys.

    3) clock.

    you certainly need clock after all.

    you need double check if the clock is correct.

    --- Quote End ---

    I'm not sure if there is something wrong with my Qsys design.

    You may look from the link http://i.imgur.com/l4vag3w.png

    It gives no errors in Qsys, it compiles but when I try and run my program it won't start.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    you have to check those.

    1) reset_n

    do you give reset signal to nios?

    at least you need to give signal which stuck high.

    or a pulse it becomes low once is better.

    2)JTAG uart.

    if your Qsys does not have JTAG uart.

    you have no way to connect with your Qsys.

    3) clock.

    you certainly need clock after all.

    you need double check if the clock is correct.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    I get the same error with a simple design. First I had to increase the on-chip memory to 64 K.

    Now I see Nios doesn't start. Maybe I have some design error. How can I know?

    $ nios2-download -g /home/developer/proj/quartus0423/software/nios2hello/nios2hello.elf
    Using cable "USB-Blaster ", device 1, instance 0x00
    Pausing target processor: not responding.
    Resetting and trying again: FAILED
    Leaving target processor paused
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    I am suspecting that the Nios didn't manage to boot up (from the message above). Perhaps you can try a simple Nios design that boots from on-chip memory to confirm this.