• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 546 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.

Original question:

local db of gateway is cleared/empty/corrupted

BEAGLEBK: local db of gateway is cleared/empty/corrupted

Ahmad.TI
Expert 1780 points

Part Number: BEAGLEBK

Hello, I have encountered the same problem as this post but no result is obtained.

"If I remove the power supply of beagle bone for particular instances the DbDeviceInfo.csv, DbEndpoints.csv, files in /Precompiled_arm/servers/ directory either gets empty or changed with some random values (number of '@' characters appended) which results in auto removing of devices from gateway."

Isn't there any way to solve this? Where do this .csv files are used in the source code?

  • 0
    TI__Intellectual 2780 points

    Removing the power supply from a computer which is writing files on it will almost always result in some sort of corruption/damage. Why are you removing the power from something which is meant to be always on?

    EDIT: The only suggestion I have is to look to see if there is some sort of detection hook which you're able to use to detect and unmount the SD card right before the board is shutdown.

  • 0 in reply to Sean M
    Expert 1780 points

    It may be happen in real as it happened for me. For example if the BBB looses its power supply suddenly and no battery is connected to it. I think one way to solve this is to take backup this files but I don't know where they are create or modified or are read.

  • 0 in reply to Sean M
    Expert 1780 points
    Is there any way to read or write contents of internal databases of gateway subsystem?
  • 0 in reply to Ahmad.TI
    TI__Intellectual 2780 points

    Ahmad,

    The ZNP device maintains its own device list independently of the csv files, so even if they are corrupted, the ZNP should still be able to keep track of the device list. Maybe a work around you're able to do is on the application side, try and query the ZNP device's association table to restore that information?

    You'd just simply use standard linux commands to write to the csv, for example write().


    However, this is more of a BeagleBone issue, I'm not really sure if we're able to do much about this.

    Best,
    Sean