Executable file system for an embedded computer

• US 20040044708A1
• Filed: 08/27/2002
• Published: 03/04/2004
• Est. Priority Date: 08/27/2002
• Status: Active Grant

• Current Assignee: Aptiv Technologies Limited (Aptiv PLC)
• Original Assignee: Delphi Technologies, Inc. (BorgWarner Incorporated)
• Inventors: Linke, Scott L., Bailey, Kirk A.
• Granted Patent: US 7,178,139 B2
• Time in Patent Office: Days
• US Class Current: 707/205
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

Binary files in an executable file system can be directly executed by the central processing unit at the location in which the binary files are stored. A pre-runtime tool can traverse a replica directory hierarchy in a host/loading computer to fill an internal data structure which can be used to generate a binary file that can be loaded directly into the embedded computer. The central processing unit (CPU) and its components such as the address bus, data bus, and program counter, can directly interact with unit of storage interface mechanisms, such as read/write means, identifying location means, and concatenation means. In some embodiments, the page size in the memory management unit (MMU) of the CPU is set to the same size as the unit of storage.

Claims

1. A method for creating an executable file system with a software component in an embedded computer, the method comprising:

generating the software component;

resolving dependencies for the software component; and

loading the software component as a binary file, wherein a non-binary copy of the software component is not loaded.

2. The method of claim 1, wherein the software component is an executable file.

3. The method of claim 1, wherein the software component is a shared library component.

4. The method of claim 1, wherein the software component is generated by a computer.

5. The method of claim 1, wherein a host computer loads the software component into the embedded computer.

6. The method of claim 1, further comprising setting a page size in a memory management unit in a central processing unit of the embedded computer.

7. The method of claim 6, wherein the page size is set to equal a unit of storage in a file system.

8. The method of claim 1, further comprising creating a replica directory hierarchy in a host computer that mirrors a director hierarchy in the embedded computer.

9. The method of claim 8, further comprising traversing the replica directory hierarchy with a tool.

10. The method of claim 9, further comprising populating an internal data structure with the tool.

11. The method of claim 10, further comprising constructing a binary file with the internal data structure.

12. The method of claim 1, further comprising mapping a direct path between a central processing unit and a means for locating units of storage in a file system.

13. The method of claim 1, further comprising mapping a direct path between a central processing unit and a means for accessing units of storage in a file system.

14. The method of claim 1, further comprising mapping a direct path between a central processing unit and a means for concatenating units of storage.

15. A system for loading executable file systems into an embedded computer, comprising:

an embedded computer, including a directory hierarchy; and

a host computer, including a replica hierarchy, a pre-runtime tool, and a binary file;

wherein said pre-runtime tool generates said binary file from said replica hierarchy; and

wherein said host computer loads said binary file into said embedded computer.

16. The system of claim 15, said host computer further comprising an internal data structure, wherein said pre-runtime tool fills said internal data structure with said replica hierarchy, and wherein said binary file is created with said internal data structure.

17. A computer comprising:

a plurality of software components;

wherein each software component in said plurality of software components is in a form of a binary file; and

wherein said computer comprises no non-binary copies of any software components.

18. The system of claim 17, further comprising:

a unit of storage;

a central processing unit; and

a file system, including a unit of storage interface.

19. The system of claim 18, wherein said central processing unit controls said unit of storage interface.

20. The system of claim 19, wherein said central processing unit directly controls said unit of storage interface.

21. The system of claim 19, wherein said unit of storage interface is a read/write means.

22. The system of claim 19, wherein said unit of storage interface is an identifying location means.

23. The system of claim 19, wherein said unit of storage interface is a concatenation means.

24. The system of claim 19, wherein said unit of storage interface includes a read/write means, an identifying location means, and a concatenation means.

25. The system of claim 18, wherein said central processing unit includes a page size set to said unit of storage.

26. The system of claim 18, wherein said central processing unit includes an address bus;

wherein said file system includes a concatenation means; and

wherein a concatenation of said unit of storage is consistent said address bus.

27. The system of claim 18, wherein said unit of storage does not contain a file system link to any other units of storage in said embedded computer.