![]() And while the firmware is about 11MiB large, it is compressed only about 1/3 of that, so the current firmware versions do fit comfortably. The allows up to 8MiB for the firmware data. This area contains three full copies of the firmware at sector 0x0000, 0x4000 and 0x8000 within this area. The firmware image area, about 32MiB in size.The first sector of the file has a copy of the FS Information Sector, the rest is filled with zeros. A 5 sector reserved area at the beginning.Again: either a bug or a safety margin.īecause of these data structures, it is not enough to copy the file from the SD card, you should always make an image copy of the whole SD card, never just a copy of the LOXONE1.FS! That said: you could write a new FS Information Sector sector with the info from above to get it to work with the Miniserver, but this is not really a clean solution. The size of the filesystem in sectors seems to be a bit less than the actual size of the LOXONE1.FS file. More to that below at the transaction record. Mode for the transaction cache, typically 0. Might be the number of sectors per cluster, but this is hardcoded in the filesystem and this value is not used. This value minus the one in 0x1D4 is the size of the filesystem in sectors. Offset behind the filesystem relative to the filesystem start. 64MiB), which feels like a bug, because the additional 5 is not needed and already part of the reserved sectors, but it also doesn't harm. Number of sectors reserved for the firmware image. Number of reserved sectors, they are ignored, typically a value like 5. Loxone stores private information right in front of the middle signature at the 0x01E4 offset: Offsetīase sector pointing to the begining of the LOXONE_SD file. The content of this sector is ignored, besides the 3 signatures, which are used to validate it. If it can't be found, the boot will fail. In that volume the FS Information Sector is loaded again. If it can't be detected, it will assume the SD card has a Master Boot Record (MBR) in sector #0 and pull the start sector for volume #0 from it. ![]() The wrapping file system on the SD card is ignored by the Miniserver, it only looks for the FS Information Sector, which is expected in sector #1, following directly after the boot record in sector #0. The LOXONE1.FS file contains the custom Loxone file system, which is as far as I know, not supported by any software, but the Miniserver. Probably a safety margin or rounding error. a one cluster directory with two entries: LOXONE_SD as the volume label and a LOXONE1.FS file.a FAT32 with 955 sectors, starting at sector #32 (directly after the hidden sectors).a copy of the FS Information sector #1 in sector #7 (ignore by the Miniserver).a copy of the boot sector #0 in sector #6.3911551 sectors (a bit more than 1.9GB). ![]() The FAT32 system on a 2GB memory card is pretty standard: You can not just copy this file onto a different disk, because the FS Information Sector needs to point to it and it can't be fragmented in any way. It is addressed directly, the FAT32 filesystem is ignored. It contains a single file 'LOXONE_SD', which occupies the whole medium. The Micro-SD card is a standard 2GB memory card with a FAT32 filesystem on it. This filesystem is only accessed by the Miniserver firmware. The SD card also contains the file system, which is used for the configuration, the web server and all additional files, like statistics. The Miniserver loads the firmware from the SD card via a little boot loader, which exists in the flash memory on the board. Dont' forget to always make a full backup of your SD card first! Intro
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |