• State TI Thinks Resolved
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 178 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

DRA829V: watchdog - dra829

DRA829V: QNX DRA829V

Charan cherry
Prodigy 40 points
Part Number: DRA829V

Tool/software:

The offsets i mentioned are in the TRM and iam using RTI0 instance . i want help for below issue

i am seeing status register setting window violation bit but system reset not occurring even though i configured reaction control register as reset

  • 0
    TI__Mastermind 48123 points

    Hi, 

    In the related previous post, you mentioned "in QNX moments ide by in and out functions." How are you doing this? Can you share details on this?

    Charan cherry said:
    The offsets i mentioned are in the TRM and iam using RTI0 instance .

    Okay, thanks for letting us know.

    However, we still need more information to support your query. Please provide all the necessary details in your query. Since you say QNX, tell us what TI SDK version is being used. What is the bootloader being used? Have you ensured that no one else uses this instance (RTI0)?

    Let us know.

    Thanks.

  • 0 in reply to Praveen Rao
    Prodigy 40 points

    no one else uses this instance (RTI0).

  • 0 in reply to Charan cherry
    Prodigy 40 points

    PROCESSOR-SDK-QNX-J721E Version: 09.02.00.04 version

  • 0 in reply to Charan cherry
    TI__Mastermind 48123 points

    OK. Please share details for other questions posted above.

    Thanks.

  • 0 in reply to Praveen Rao
    TI__Prodigy 640 points

    Which part of the code should be under IO privileges?

    Either the Watchdog Initialization code or the Watchdog feed or both.

    Currently, we are able to perform the initialization and verify the registers with correct values. But the down timer is not getting updated.

  • 0 in reply to Anatya Vallabh
    TI__Mastermind 48123 points
    Anatya Vallabh said:
    Which part of the code should be under IO privileges?

    Any thread that needs to access IO space registers needs to have IO privileges. So if the QNX process has multiple threads, and each tries to access these registers, then we need to make sure each has these privileges.

    Suggest looking into the QNX BSP and/or QNX documentation on how this is done. If it is not clear, suggest contacting QNX directly about the usage.  Note that the QNX BSP for J721E already has the wdtkick-j7 driver. see the path <bsp>/src/hardware/support/wdtkick-j7.

    Thanks.

  • 0 in reply to Praveen Rao
    Prodigy 100 points

    Hi Praveen,

    We have added the following line of code to enable the IO privileges. But nothing changed.

    ThreadCtl(_NTO_TCTL_IO_LEVEL, _NTO_IO_LEVEL_2)

    We didn't find any source code for wdtkick at the above mentioned location in BSP_ti-j721e-tda4vm-sk_br-710_be-710_SVN981674_JBN18.

    Our design is based on evm BSP and we are trying to have watchdog enabling and kick in our application.

  • 0 in reply to Rajashekar Reddy R
    TI__Mastermind 48123 points
    Rajashekar Reddy R said:
    We have added the following line of code to enable the IO privileges. But nothing changed.

    What does not change? Please 

    Rajashekar Reddy R said:

    We didn't find any source code for wdtkick at the above mentioned location in BSP_ti-j721e-tda4vm-sk_br-710_be-710_SVN981674_JBN18.

    I see that you are looking into the J721E SK BSP. Please note that the TI PSDK QNX release does not support this SK board. For support, you must contact QNX directly.

    We were refering to the J721E EVM QNX BSP --> QNX BSP: BSP_ti-j721e-am752x-evm_be-800_SVN1018405_JBN318.zip or BSP_ti-j721e-am752x-evm-ioscok_br-710_be-710_SVN1013995_JBN15.zip, which is available on QNX Software Center.

    Thanks.

  • 0 in reply to Praveen Rao
    Prodigy 100 points

    Hi Praveen,

    We are using QNX 7.1 and we have access only to the below J721E BSPs,

    BSP_ti-j721e-am752x-evm_br-710_be-710_SVN927158_JBN10

    BSP_ti-j721e-tda4vm-sk_br-710_be-710_SVN981674_JBN18

    The BSPs you are talking about are custom BSPs or public release.

  • 0 in reply to Rajashekar Reddy R
    TI__Mastermind 48123 points
    Rajashekar Reddy R said:
    The BSPs you are talking about are custom BSPs or public release.

    Okay, the version we referred to above may not be publicly accessible. However, you can request direct access to these BSP versions with QNX under your CSP plan.

    Thanks.