Forum Discussion

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

Application Hangs after JTAG Cable Removed

I've been working on a system that is on a Cyclone III EP3C400240C8N running a single threaded application. The SOPC contains a JTAG UART that was used for debugging purposes, and the main purpose of the system is to read/store different configuration values and communicate via the Modbus Protocol over RS232.

When I run the application with the JTAG cable connected, it can run without a hitch, however if I package the program into a .pof and program into the EPCS via Active Serial, then the system can handle roughly 50 Modbus messages before it seems to hang indefinitely.

Essentially the program seems to run correctly when launched via the NIOS II BTE, however if the program is stored in the EPCS then it will only run for a short time before hanging. I'm wondering if anyone else has had similar problems and/or has tips as to where to start looking.

5 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    I seem to have fixed the issue by lowering the JTAG Debug level on the CPU from 3 to 1. Any ideas why this would fix this?

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    Do you own a Nios license ?

    AFAIK non licensed Nios only work with JTAG connection.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    thepancake:

    Yes I know that. But it looks like he is not using QII 9.1 + Nios II/e

    Looks like he either is using an older QII or one of the NiosII/f or NiosII/s.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    obscurecaucasian mentions that he is generating a POF file which implies he does have a license.

    obscurecaucasian:

    Perhaps you have a bug in your software that is accidently writting to the slave port of the debug module. Something such as a bad pointer our out of bounds memory access could cause this.