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.

SM470R1B1M-HT: Programming error: Trace32 Laturbach Practice Stack Overflow

Part Number: SM470R1B1M-HT

Tool/software:

Hello, I am a junior engineer, and I have been working with this ARM processor. We have been running into issues when programming and this has been a reoccurring issue since its design. The unit is being programmed via JTAG port and the programming software we are using are Laturbach and Trace32. This is a fairly old design, but we have always experienced inconsistencies when programming the unit. About 1 out of every 5 units turn out with this same issue. Generally, replacing the ARM processor has showed a 50 percent success chance. We would have the failed units x-rayed and it showed no solder bridges or other manufacturing defects.

I am unsure what else to look into. I have checked for proper clock signals, proper power, there are no shorts. I have also unlimited the current from the power supply after verifying that there are no shorts. I have attached a schematic of the circuit here.

 SM470.pdf

  • Hi,

    This is a fairly old design,

    Indeed this is a very old design. 

    About 1 out of every 5 units turn out with this same issue.

      Can you elaborate what issue you are seeing? Can you show a screenshot of any error message produced by Lauterbach?

    I am unsure what else to look into. I have checked for proper clock signals, proper power, there are no shorts. I have also unlimited the current from the power supply after verifying that there are no shorts. I have attached a schematic of the circuit here.

    Does Lauterbach toolchain have utility to run a JTAG scan test? You will need to consult with Lauterbach how to invoke such an utility if available. 

    Can you use the scope to probe the JTAG signals (TCK, TMS, TDI and TDO) between the good board and the bad board? 

    Please take a look at this reference schematic for a 7SM470R1B1M EVM that is no longer available. However, you can compare the JTAG connections and especially the pull resistors on TMS, TCK and RTCK. I don't know for sure how the presence of these pull resistors will actually affect your JTAG connection but I see that you are missing them especially for the RTCK. 

    SM470R1B1M-SK_Rev.B.pdf

  • Hello Charles,

    Can you elaborate what issue you are seeing? Can you show a screenshot of any error message produced by Lauterbach?

    Yes, I am receiving a generic error message "Practice Stack Overflow" I have attached a screenshot of it here.

    Does Lauterbach toolchain have utility to run a JTAG scan test?

    Yes, it does have a JTAG toolchain, but we are getting the Practice Stack Overflow message beforehand. There is no communication between the processor and software.

    Can you use the scope to probe the JTAG signals (TCK, TMS, TDI and TDO) between the good board and the bad board? 

    We are not getting any signals from these pins on a bad board, but we are getting them on a good board.

    I don't know for sure how the presence of these pull resistors will actually affect your JTAG connection

    I checked the schematic sent in your post and noticed that the pullup resistors have NA next to them, does this mean not applicable?

    Thank you for your quick response! 

  • Hi,

      I have no idea what "Practice Stack Overflow" means by Lauterbach. You will need to consult with Lauterbach at least to understand what the message is supposed to convey. I have no experience with the tool. 

    We are not getting any signals from these pins on a bad board, but we are getting them on a good board.

    Which signal(s) are you getting and not getting on the bad boards and good boards. Please clarify.

    I checked the schematic sent in your post and noticed that the pullup resistors have NA next to them, does this mean not applicable?

    I'm not sure if NA means Not Applicable here but at least can you try it? The pull resistors are good practice to have on the JTAG. 

  • Hello,

    We took a look at the Lauterbach error messages, and this message is sent when there is no communication between the debugger and the processor, or something is interrupting the communication between the two.

    Which signal(s) are you getting and not getting on the bad boards and good boards. Please clarify.

    There are no signals coming from either of the TCK, TMS, TDI, RST, and TDO pins.

    I'm not sure if NA means Not Applicable here but at least can you try it? The pull resistors are good practice to have on the JTAG. 

     We will give this a try and report back if this helps, thanks again!

  • There are no signals coming from either of the TCK, TMS, TDI, RST, and TDO pins.

    TCK, TMS and TDI are from the debug probe. The MCU only outputs the TDO signal responding TCK/TMS/TDI inputs. Can you find out why the debug probe is not outputting these signals? Is it due to your RTCK left floating?