2017-08-01 16:19:23 +00:00
|
|
|
#ifdef TARGET_LPC1768
|
2017-06-17 21:19:42 +00:00
|
|
|
|
2017-09-06 11:28:32 +00:00
|
|
|
#include "../../inc/MarlinConfig.h"
|
2017-06-17 21:19:42 +00:00
|
|
|
|
2017-09-06 11:28:32 +00:00
|
|
|
#if ENABLED(EEPROM_SETTINGS)
|
2017-06-17 21:19:42 +00:00
|
|
|
|
2017-09-06 11:28:32 +00:00
|
|
|
#include "../persistent_store_api.h"
|
2017-08-01 16:19:23 +00:00
|
|
|
|
2017-09-06 11:28:32 +00:00
|
|
|
#include "chanfs/diskio.h"
|
|
|
|
#include "chanfs/ff.h"
|
2017-06-17 21:19:42 +00:00
|
|
|
|
2017-10-04 20:40:54 +00:00
|
|
|
extern uint32_t MSC_Aquire_Lock();
|
|
|
|
extern uint32_t MSC_Release_Lock();
|
|
|
|
|
2017-06-17 21:19:42 +00:00
|
|
|
namespace HAL {
|
|
|
|
namespace PersistentStore {
|
|
|
|
|
|
|
|
FATFS fat_fs;
|
|
|
|
FIL eeprom_file;
|
|
|
|
|
|
|
|
bool access_start() {
|
Update LPC persistent store to initialize eeprom.dat with FF
This change initialize any data in eeprom.dat beyond the current file size to FF.
That way if eeprom.dat is deleted and created again, it doesn't take the old values or random ones, but rather starts with FF in all positions as a real brand new or erased eeprom.dat
Currently if you delete eeprom.dat and restart the board, the new file is created in the same sector with the same content, since FAT does not actually delete the data, just marks the sector as free. I tested by deleting the file, and then rebooting the board, and checking the file content.
The change can be tested in the same way, deleting, rebooting the board, and then the new content should be all FF.
If an eeprom file already exist with data on it, but smaller than E2END, it will be padded with FF on first access, so it will not have random or old content appended.
2017-09-28 01:43:43 +00:00
|
|
|
UINT file_size = 0,
|
|
|
|
bytes_written = 0;
|
|
|
|
const char eeprom_zero = 0xFF;
|
2017-10-04 20:40:54 +00:00
|
|
|
MSC_Aquire_Lock();
|
Update LPC persistent store to initialize eeprom.dat with FF
This change initialize any data in eeprom.dat beyond the current file size to FF.
That way if eeprom.dat is deleted and created again, it doesn't take the old values or random ones, but rather starts with FF in all positions as a real brand new or erased eeprom.dat
Currently if you delete eeprom.dat and restart the board, the new file is created in the same sector with the same content, since FAT does not actually delete the data, just marks the sector as free. I tested by deleting the file, and then rebooting the board, and checking the file content.
The change can be tested in the same way, deleting, rebooting the board, and then the new content should be all FF.
If an eeprom file already exist with data on it, but smaller than E2END, it will be padded with FF on first access, so it will not have random or old content appended.
2017-09-28 01:43:43 +00:00
|
|
|
if (f_mount(&fat_fs, "", 1)) {
|
2017-10-04 20:40:54 +00:00
|
|
|
MSC_Release_Lock();
|
|
|
|
return false;
|
|
|
|
}
|
2017-06-17 21:19:42 +00:00
|
|
|
FRESULT res = f_open(&eeprom_file, "eeprom.dat", FA_OPEN_ALWAYS | FA_WRITE | FA_READ);
|
Update LPC persistent store to initialize eeprom.dat with FF
This change initialize any data in eeprom.dat beyond the current file size to FF.
That way if eeprom.dat is deleted and created again, it doesn't take the old values or random ones, but rather starts with FF in all positions as a real brand new or erased eeprom.dat
Currently if you delete eeprom.dat and restart the board, the new file is created in the same sector with the same content, since FAT does not actually delete the data, just marks the sector as free. I tested by deleting the file, and then rebooting the board, and checking the file content.
The change can be tested in the same way, deleting, rebooting the board, and then the new content should be all FF.
If an eeprom file already exist with data on it, but smaller than E2END, it will be padded with FF on first access, so it will not have random or old content appended.
2017-09-28 01:43:43 +00:00
|
|
|
if (res) MSC_Release_Lock();
|
|
|
|
|
|
|
|
if (res == FR_OK) file_size = f_size(&eeprom_file);
|
|
|
|
|
|
|
|
if (res == FR_OK) {
|
|
|
|
f_lseek(&eeprom_file, file_size);
|
2017-10-18 19:00:29 +00:00
|
|
|
while (file_size <= E2END && res == FR_OK) {
|
Update LPC persistent store to initialize eeprom.dat with FF
This change initialize any data in eeprom.dat beyond the current file size to FF.
That way if eeprom.dat is deleted and created again, it doesn't take the old values or random ones, but rather starts with FF in all positions as a real brand new or erased eeprom.dat
Currently if you delete eeprom.dat and restart the board, the new file is created in the same sector with the same content, since FAT does not actually delete the data, just marks the sector as free. I tested by deleting the file, and then rebooting the board, and checking the file content.
The change can be tested in the same way, deleting, rebooting the board, and then the new content should be all FF.
If an eeprom file already exist with data on it, but smaller than E2END, it will be padded with FF on first access, so it will not have random or old content appended.
2017-09-28 01:43:43 +00:00
|
|
|
res = f_write(&eeprom_file, &eeprom_zero, 1, &bytes_written);
|
|
|
|
file_size++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (res == FR_OK) {
|
|
|
|
f_lseek(&eeprom_file, 0);
|
|
|
|
f_sync(&eeprom_file);
|
|
|
|
}
|
|
|
|
return res == FR_OK;
|
2017-06-17 21:19:42 +00:00
|
|
|
}
|
|
|
|
|
2017-09-06 11:28:32 +00:00
|
|
|
bool access_finish() {
|
2017-06-17 21:19:42 +00:00
|
|
|
f_close(&eeprom_file);
|
|
|
|
f_unmount("");
|
2017-10-04 20:40:54 +00:00
|
|
|
MSC_Release_Lock();
|
2017-06-17 21:19:42 +00:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2017-10-18 19:00:29 +00:00
|
|
|
// File function return codes for type FRESULT This goes away soon. But it is helpful right now to see
|
|
|
|
// the different errors the read_data() and write_data() functions are seeing.
|
|
|
|
//
|
|
|
|
//typedef enum {
|
|
|
|
// FR_OK = 0, /* (0) Succeeded */
|
|
|
|
// FR_DISK_ERR, /* (1) A hard error occurred in the low level disk I/O layer */
|
|
|
|
// FR_INT_ERR, /* (2) Assertion failed */
|
|
|
|
// FR_NOT_READY, /* (3) The physical drive cannot work */
|
|
|
|
// FR_NO_FILE, /* (4) Could not find the file */
|
|
|
|
// FR_NO_PATH, /* (5) Could not find the path */
|
|
|
|
// FR_INVALID_NAME, /* (6) The path name format is invalid */
|
|
|
|
// FR_DENIED, /* (7) Access denied due to prohibited access or directory full */
|
|
|
|
// FR_EXIST, /* (8) Access denied due to prohibited access */
|
|
|
|
// FR_INVALID_OBJECT, /* (9) The file/directory object is invalid */
|
|
|
|
// FR_WRITE_PROTECTED, /* (10) The physical drive is write protected */
|
|
|
|
// FR_INVALID_DRIVE, /* (11) The logical drive number is invalid */
|
|
|
|
// FR_NOT_ENABLED, /* (12) The volume has no work area */
|
|
|
|
// FR_NO_FILESYSTEM, /* (13) There is no valid FAT volume */
|
|
|
|
// FR_MKFS_ABORTED, /* (14) The f_mkfs() aborted due to any problem */
|
|
|
|
// FR_TIMEOUT, /* (15) Could not get a grant to access the volume within defined period */
|
|
|
|
// FR_LOCKED, /* (16) The operation is rejected according to the file sharing policy */
|
|
|
|
// FR_NOT_ENOUGH_CORE, /* (17) LFN working buffer could not be allocated */
|
|
|
|
// FR_TOO_MANY_OPEN_FILES, /* (18) Number of open files > FF_FS_LOCK */
|
|
|
|
// FR_INVALID_PARAMETER /* (19) Given parameter is invalid */
|
|
|
|
//} FRESULT;
|
|
|
|
|
2017-06-17 21:19:42 +00:00
|
|
|
bool write_data(int &pos, const uint8_t *value, uint16_t size, uint16_t *crc) {
|
2017-10-18 19:00:29 +00:00
|
|
|
FRESULT s;
|
2017-06-17 21:19:42 +00:00
|
|
|
UINT bytes_written = 0;
|
2017-10-18 19:00:29 +00:00
|
|
|
s = f_lseek(&eeprom_file, pos);
|
|
|
|
if ( s ) {
|
|
|
|
SERIAL_PROTOCOLPAIR(" write_data(", pos); // This extra chit-chat goes away soon. But it is helpful
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) value); // right now to see errors that are happening in the
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) size); // read_data() and write_data() functions
|
|
|
|
SERIAL_PROTOCOL("...)\n");
|
|
|
|
SERIAL_PROTOCOLPAIR(" f_lseek()=", (int) s);
|
|
|
|
SERIAL_PROTOCOL("\n");
|
|
|
|
return s;
|
|
|
|
}
|
|
|
|
s = f_write(&eeprom_file, (void *)value, size, &bytes_written);
|
|
|
|
if ( s ) {
|
|
|
|
SERIAL_PROTOCOLPAIR(" write_data(", pos); // This extra chit-chat goes away soon. But it is helpful
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) value); // right now to see errors that are happening in the
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) size); // read_data() and write_data() functions
|
|
|
|
SERIAL_PROTOCOL("...)\n");
|
|
|
|
SERIAL_PROTOCOLPAIR(" f_write()=", (int) s);
|
|
|
|
SERIAL_PROTOCOL("\n");
|
|
|
|
SERIAL_PROTOCOLPAIR(" size=", (int) size);
|
|
|
|
SERIAL_PROTOCOLPAIR("\n bytes_written=", (int) bytes_written);
|
|
|
|
SERIAL_PROTOCOL("\n");
|
|
|
|
return s;
|
|
|
|
}
|
2017-06-17 21:19:42 +00:00
|
|
|
crc16(crc, value, size);
|
|
|
|
pos = pos + size;
|
2017-10-18 19:00:29 +00:00
|
|
|
return (bytes_written != size); // return true for any error
|
2017-06-17 21:19:42 +00:00
|
|
|
}
|
|
|
|
|
2017-10-18 19:00:29 +00:00
|
|
|
bool read_data(int &pos, uint8_t* value, uint16_t size, uint16_t *crc) {
|
2017-06-17 21:19:42 +00:00
|
|
|
UINT bytes_read = 0;
|
2017-10-18 19:00:29 +00:00
|
|
|
FRESULT s;
|
|
|
|
s = f_lseek(&eeprom_file, pos);
|
|
|
|
if ( s ) {
|
|
|
|
SERIAL_PROTOCOLPAIR(" read_data(", pos); // This extra chit-chat goes away soon. But it is helpful
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) value); // right now to see errors that are happening in the
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) size); // read_data() and write_data() functions
|
|
|
|
SERIAL_PROTOCOL("...)\n");
|
|
|
|
SERIAL_PROTOCOLPAIR(" f_lseek()=", (int) s);
|
|
|
|
SERIAL_PROTOCOL("\n");
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
s = f_read(&eeprom_file, (void *)value, size, &bytes_read);
|
|
|
|
if ( s ) {
|
|
|
|
SERIAL_PROTOCOLPAIR(" read_data(", pos); // This extra chit-chat goes away soon. But it is helpful
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) value); // right now to see errors that are happening in the
|
|
|
|
SERIAL_PROTOCOLPAIR(",", (int) size); // read_data() and write_data() functions
|
|
|
|
SERIAL_PROTOCOL("...)\n");
|
|
|
|
SERIAL_PROTOCOLPAIR(" f_write()=", (int) s);
|
|
|
|
SERIAL_PROTOCOL("\n");
|
|
|
|
SERIAL_PROTOCOLPAIR(" size=", (int) size);
|
|
|
|
SERIAL_PROTOCOLPAIR("\n bytes_read=", (int) bytes_read);
|
|
|
|
SERIAL_PROTOCOL("\n");
|
|
|
|
return true;
|
|
|
|
}
|
2017-06-17 21:19:42 +00:00
|
|
|
crc16(crc, value, size);
|
|
|
|
pos = pos + size;
|
2017-10-18 19:00:29 +00:00
|
|
|
return bytes_read != size; // return true for any error
|
2017-06-17 21:19:42 +00:00
|
|
|
}
|
|
|
|
|
2017-09-06 11:28:32 +00:00
|
|
|
} // PersistentStore
|
|
|
|
} // HAL
|
2017-06-17 21:19:42 +00:00
|
|
|
|
|
|
|
#endif // EEPROM_SETTINGS
|
2017-09-06 11:28:32 +00:00
|
|
|
#endif // TARGET_LPC1768
|