• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 223 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320C6410 Error 0x80000262/-1154

Ryusuke Okabe
Prodigy 10 points
Part Number: TMS320C6410

Tool/software:

I'm using CCS v3.3.
I'm using v3.3 because we don't have the manpower or the man-hours, and I haven't had any problems so far.

Computer: Windows7 32bit (using XP mode)

Antivirus software: Virus Buster

CCS version: 3.3.38.2

Emulator SEEDXDS510PLUS Emulator (used for about 5 years): Third party product

External memory Flash memory S29AL008J70TFI010   Infineon

○I don't know the details of the error.
I think it probably means that the DSP cannot be recognized from the writing environment CCS3.3...
Is there any more information or anything you can think of?

The error display is as follows.

"

Error connecting to the target:

Error 0x80000262/-1154

Fatal Error during: Memory.  Execution . Initialization. OCS.

The memory at 0x00000000 continually indicated it was 'not ready'

The emulator was unable to regain control of the processor.

The processor must be reset.

Sequence ID: 0

Error Code: -1154

Error Class: 0x80000262


This is a board whose design has not changed for about 10 years.
We have been producing about 100 pieces a year,
Regarding boards produced after May 2023,
An event has occurred where the emulator for writing software cannot be connected.

  • 0
    TI__Genius 11425 points

    Hi Ryusuke,

    Do you have access to another SEEDXDS510PLUS Emulator to determine if you see the same error message using another emulator?

    Similarly, do you see the same issue if you use a different TMS320C6410 board?

    I'm trying to see if we can determine if it is an issue with a specific emulator or board, or something other issue.

    Thank you,

    Ricky

  • 0 in reply to Ricky Lau
    Prodigy 10 points

    Hi Ricky,

    Thanks for your reply.

    I was unable to access the target board using another emulator. Same error occurs.

    When trying another TMS320C6410 board, 200 boards in stock made after May 2023 occur the same error.

    Boards made before May 2023 can be accessed.

    Thanks,

    Ryusuke

  • 0 in reply to Ryusuke Okabe
    TI__Genius 11425 points

    Ryusuke,

    Since you are able to connect to older boards (pre May 2023) using the same emulator and same CCS version, it sounds like there might have been some manufacturing issues that was introduced in May 2023 that is affecting the new boards.

    I'm asking experts in the office to see if I can gather more information on the specific error message right now, while can hopefully isolate the issue more. But since it is quite an old version of CCS, it will likely take some time to do the investigation. I'll keep you updated on any information we find.

    Thank you,

    Ricky

  • 0 in reply to Ricky Lau
    Prodigy 10 points

    Dear  Ricky

    Thank you for your investigation.

    I have checked the serial number engraved on the surface of the DSP, so I will write it down. I hope it will be of some use.

    DSP that can be accessed
    CA-0AAS3FW (before May 2023)

    DSP that cannot be connected (after May 2023)
    CA-28A68PW
    CA-34CLXIW
    CA-34CLVZW
    CA-38CK6SW
    CA-28A2JCW

    Thank you,

    Ryusuke

  • 0 in reply to Ryusuke Okabe
    TI__Genius 11425 points

    Ryusuke,

    Thanks for providing the additional information. I'll let you know if we find out any more information about the error message.

    Thanks,

    Ricky

  • 0 in reply to Ricky Lau
    Prodigy 10 points

    Hi Ricky,

    Problem solved.

    No processing had been done for the part that shares the bus with the ROM to which the program is written.

    When processing of this part was performed,
    the connection between the emulator and DSP was successfully completed.

    The causal relationship is still unclear, but it was caused by not following the work flow.

    I am very grateful for your cooperation in this matter.

    Thanks,

    Ryusuke