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

DM385: Hardware Exception after ISS Reset

Eduard Krasnov
Prodigy 50 points

Part Number: DM385
Other Parts Discussed in Thread: SYSCONFIG

Hello,

i am working on a system, based on DM385 and IPNC_RDK and  have a problem by changing of sensor resolution during runtime - the software crashes with a hardware exception.

The workflow by changing resolution - stop ISS, reconfig to the new resolution, start ISS.

i try now to reset ISS in the ISS Stop function Iss_captStop() to have the same behaviour as by system start :

    iss_regs->ISS_HL_SYSCONFIG |= 0x1;

But the hardware exception is caused immediately after ISS reset. What can be the reason?

Thank you in advance.

  • 0
    TI__Guru**** 151684 points
    Hi,

    I think there is need to perform more experiments to get a better understanding for this behavior.

    Here are some potential experiments

    1) During normal operation (without changing the sensor resolution) can you try to reset the ISS and check the behavior?

    2) When the hardware exception occurs, read status registers to get better understanding of the exception

    thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 50 points

    HI Cesar,

    thank you for the reply.

    Which status registers (M3 or ISS) do you mean?  And what kind of information can we get there, that can help to understand the reason of exception?

    To my original problem:  i gave up the idea to reset ISS, because it is not correct in this case - Different Links (Camera, OSD, VNF..)

     are dealing with ISS  and will not be aware of the ISS reset.

    The problem of changing sensor's resolution in rutime is solved now. The problem was in the initializing of H3A - it was always (re)inited with original resolution, the system started with.

    Best regards,

    Eduard