1 |
<meino.cramer <at> gmx.de> writes: |
2 |
|
3 |
|
4 |
> I have an embedded system with internal flash memory. |
5 |
> The internal flash memory contains some static files, |
6 |
> which are only be read and others, which get written |
7 |
> from time to time. |
8 |
|
9 |
|
10 |
Embedded systems vary wildly. If you can you need to be |
11 |
as specific as possilble on which embedded system, processor |
12 |
model, vendor, version etc. |
13 |
|
14 |
> The internal flash has a FAT32-formatted filesystem |
15 |
> and no real partiton (the device is directly fomratted |
16 |
> as so often with this kind of lash memories. |
17 |
> From time to time the software crashes while updateing |
18 |
> some files (writing to them) leaving a unclean filesystem |
19 |
> behind. |
20 |
|
21 |
|
22 |
> Often -- after fscking the filesystem -- files named |
23 |
> FSCK<number>.REC are left in the root of the filesystem. |
24 |
|
25 |
Have you sought out help from the vendor/manufacture? |
26 |
|
27 |
Can the embedded OS be updated and maintained? |
28 |
|
29 |
Can you install another, better supported embedded OS |
30 |
like openWRT |
31 |
|
32 |
https://openwrt.org/ |
33 |
|
34 |
> Is it correct to assume, that only those files are |
35 |
> affected by correcting the filesysten which were written/updated |
36 |
> before or is there any chance, that other, only read files |
37 |
> are also affected? |
38 |
|
39 |
You've got to get really specific on the details of the embedded OS |
40 |
and such details..... |
41 |
|
42 |
|
43 |
hth, |
44 |
James |