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

DM816x DVR SATA drive not recognised

PaulMartin
Prodigy 20 points

I'm running the NVR from DVR RDK 04.00.00.03 on a DM814x Mistral eval board.

I'm having an issue with the SATA drive.

The drive is mounted, and can be formatted via the NVR GUI, with idx and bkt files created.

 root@dm814x:/opt/dvr_rdk/ti814x# ls /media/sda1/

00000001.bkt  00000016.idx  00000032.bkt  00000047.idx  00000063.bkt  00000078.idx

00000001.idx  00000017.bkt  00000032.idx  00000048.bkt  00000063.idx  00000079.bkt

00000002.bkt  00000017.idx  00000033.bkt  00000048.idx  00000064.bkt  00000079.idx

00000002.idx  00000018.bkt  00000033.idx  00000049.bkt  00000064.idx  00000080.bkt

00000003.bkt  00000018.idx  00000034.bkt  00000049.idx  00000065.bkt  00000080.idx

00000003.idx  00000019.bkt  00000034.idx  00000050.bkt  00000065.idx  00000081.bkt

00000004.bkt  00000019.idx  00000035.bkt  00000050.idx  00000066.bkt  00000081.idx

00000004.idx  00000020.bkt  00000035.idx  00000051.bkt  00000066.idx  00000082.bkt

00000005.bkt  00000020.idx  00000036.bkt  00000051.idx  00000067.bkt  00000082.idx

00000005.idx  00000021.bkt  00000036.idx  00000052.bkt  00000067.idx  00000083.bkt

00000006.bkt  00000021.idx  00000037.bkt  00000052.idx  00000068.bkt  00000083.idx

00000006.idx  00000022.bkt  00000037.idx  00000053.bkt  00000068.idx  00000084.bkt

00000007.bkt  00000022.idx  00000038.bkt  00000053.idx  00000069.bkt  00000084.idx

00000007.idx  00000023.bkt  00000038.idx  00000054.bkt  00000069.idx  00000085.bkt

00000008.bkt  00000023.idx  00000039.bkt  00000054.idx  00000070.bkt  00000085.idx

00000008.idx  00000024.bkt  00000039.idx  00000055.bkt  00000070.idx  00000086.bkt

00000009.bkt  00000024.idx  00000040.bkt  00000055.idx  00000071.bkt  00000086.idx

00000009.idx  00000025.bkt  00000040.idx  00000056.bkt  00000071.idx  00000087.bkt

00000010.bkt  00000025.idx  00000041.bkt  00000056.idx  00000072.bkt  00000087.idx

00000010.idx  00000026.bkt  00000041.idx  00000057.bkt  00000072.idx  00000088.bkt

00000011.bkt  00000026.idx  00000042.bkt  00000057.idx  00000073.bkt  00000088.idx

00000011.idx  00000027.bkt  00000042.idx  00000058.bkt  00000073.idx  00000089.bkt

00000012.bkt  00000027.idx  00000043.bkt  00000058.idx  00000074.bkt  00000089.idx

00000012.idx  00000028.bkt  00000043.idx  00000059.bkt  00000074.idx  bktmgr.udf

00000013.bkt  00000028.idx  00000044.bkt  00000059.idx  00000075.bkt  lost+found

00000013.idx  00000029.bkt  00000044.idx  00000060.bkt  00000075.idx  topmgr.udf

00000014.bkt  00000029.idx  00000045.bkt  00000060.idx  00000076.bkt

00000014.idx  00000030.bkt  00000045.idx  00000061.bkt  00000076.idx

00000015.bkt  00000030.idx  00000046.bkt  00000061.idx  00000077.bkt

00000015.idx  00000031.bkt  00000046.idx  00000062.bkt  00000077.idx

00000016.bkt  00000031.idx  00000047.bkt  00000062.idx  00000078.bkt

root@dm814x:/opt/dvr_rdk/ti814x#

 

However, after file creation I get an error:

 

app: basket creation ... done 89

[BKTREC] - basket_rec.c(2017):  BKTREC_exit:Failed close basket file and index file. Already basket file is closed.

err: BKTREC_exit() Error !!!!

[BKTREC] - basket_rec.c(2017):  BKTREC_exit:Failed close basket file and index file. Already basket file is closed.

err: BKTREC_exit() Error !!!!

 

This leaves the drive state as DONE_FORMAT rather than DONE_EXT3 which the code needs to continue.

 

More drive info:

 

root@dm814x:/opt/dvr_rdk/ti814x# df

Filesystem           1K-blocks      Used Available Use% Mounted on

192.168.115.66:/home/ge/dvrrdk/DVRRDK_04.00.00.03/target/rfs_814x

                     230582528  15015680 203853824   7% /

devtmpfs                 35900       176     35724   0% /dev

none                     36016         0     36016   0% /dev/shm

tmpfs                    16384        80     16304   0% /var/volatile

tmpfs                    16384         0     16384   0% /media/ram

/dev/sda1             58589628    184664  55475112   0% /media/sda1

 

Much of the code I need visibility of is in dvr_disk.c, which I have no source code for, as it’s bundled in the NVRSOURCE release as a binary library: DVRRDK_04.00.00.03\dvr_rdk\dvrapp\shlib\dvr_disk.a

Any ideas what is going wrong and how to fix this?

Can I get access to source code for the above shared libraries (DVRRDK_04.00.00.03\dvr_rdk\dvrapp\shlib)?

Thanks,

Paul

  • 0
    TI__Guru 59700 points

    Can you confirm you are using 814x and not 816x as indicated in the title of the post.

    Pls share the dmesg logs in the failure case.

    Have you received the NVRSOURCE package from TI FAE ? Does it have the file basket_rec.c in it ?

     

  • 0 in reply to Badri Narayanan
    Prodigy 20 points

    Hi, yes, it's on a dm814x, dmesg attached.

    Yes, I have the NVRSOURCE package from TI FAE. It does have the file basket_rec.c in it. It also includes binary library files for which I have no source, eg dvr_disk.a Can I get access to source for these?

    Thanks, Paul

     

  • 0 in reply to PaulMartin
    TI__Expert 6505 points

    Hi Paul,

    The dvr_disk.a library has few disk utilities which are used to determine the size of each partision, free size available etc. This library was developed by UD Works who had designed the DVR/NVR GUI application on DM816X/DM810X.

    UD Works reserves the right to share the source code of this utility to customers who have purchased DM816x/DM810x reference design from them. TI does not have authority to share the source code of this library.

    I suggest you to contact UD Works directly to gain access to source code of this library.

    Regards,

    Arun