• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 22 subscribers
  • Views 814 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Accessing external memory

Priyadarshini Uthayakumar

Hi all

I am presently working on accessing external memory. For my project, I have to find the address of a file stored in SD card.I am using ARM controller. I am using KEIL MDK to program it.

Can anyone help me in finding the location.

Thank you in advance.

Parents
  • 0

    The normal meaning of external memory, is direct-access code or data memory outside the processor.

    Not a serially connected SD-card that you handle similar to a hard disk, by formatting it and reading/writing sectors of data.

    So you need to learn how to read sectors of data from that SD card.
    And how to detectt if the card is formatted with a file system you understand.
    Then evaluate the contents of the data structures on the file system, to figure out where the file is stored.

    Most people just buy a file system implementation, or look for one freely available implementation. Then they don't care about the actual storage location of files on the card - it's enough to be able to fopen() the file for fseek()/fread()/fwrite(), or unlink() it.

    But your project must be better specified than what you managed to present in your original post. And if it's _your_ project, the goal must somehow be for _you_ to do the task or it wouldn't be your project, would it?

Reply
  • 0

    The normal meaning of external memory, is direct-access code or data memory outside the processor.

    Not a serially connected SD-card that you handle similar to a hard disk, by formatting it and reading/writing sectors of data.

    So you need to learn how to read sectors of data from that SD card.
    And how to detectt if the card is formatted with a file system you understand.
    Then evaluate the contents of the data structures on the file system, to figure out where the file is stored.

    Most people just buy a file system implementation, or look for one freely available implementation. Then they don't care about the actual storage location of files on the card - it's enough to be able to fopen() the file for fseek()/fread()/fwrite(), or unlink() it.

    But your project must be better specified than what you managed to present in your original post. And if it's _your_ project, the goal must somehow be for _you_ to do the task or it wouldn't be your project, would it?

Children