I bumped the partition size for FAT to 128K and that seemed to work. I'll test that again with encryption enabled when I get a chance, but I expect it should be fine as I realized later I had been getting the same issue without it as well.
Thanks!
Search found 20 matches
- Fri Oct 13, 2017 12:13 pm
- Forum: ESP-IDF
- Topic: Wear leveling / FAT failed to mount
- Replies: 8
- Views: 12177
- Thu Oct 12, 2017 6:00 pm
- Forum: ESP-IDF
- Topic: Wear leveling / FAT failed to mount
- Replies: 8
- Views: 12177
Re: Wear leveling / FAT failed to mount
I tried it with encryption enabled, on a FAT partition with size 84K (512B sector size, which should be >128 sectors). I now get the following error: W (263) vfs_fat_spiflash: f_mount failed (13) I (263) vfs_fat_spiflash: Formatting FATFS partition E (263) vfs_fat_spiflash: f_mkfs failed (14) Error ...
- Thu Oct 12, 2017 12:57 pm
- Forum: ESP-IDF
- Topic: Wear leveling / FAT failed to mount
- Replies: 8
- Views: 12177
Re: Wear leveling / FAT failed to mount
I tried adjusting to different partition sizes, eventually just copying the table from the wear levelling example. It appears that no matter what, I get the same error while using the encrypted flag. For development, I don't actually have encryption enabled yet; I had assumed that the flag would be ...
- Thu Oct 12, 2017 2:19 am
- Forum: ESP-IDF
- Topic: Wear leveling / FAT failed to mount
- Replies: 8
- Views: 12177
Re: Wear leveling / FAT failed to mount
Does that minimum sector count always assume the sector size is 4096B? i.e. is the minimum sector count 1024 with 512B sectors, or would 128 sectors still be fine? As I understand, the ability to set 512B sectors is made possible by the wear-levelling layer, but I'm not sure what influence it has ov...
- Wed Oct 11, 2017 5:01 pm
- Forum: ESP-IDF
- Topic: Wear leveling / FAT failed to mount
- Replies: 8
- Views: 12177
Wear leveling / FAT failed to mount
I'm getting an error I can't track down when trying to mount a FAT partition with wear leveling. The error is as follows: E (657) wl_flash: initSections(269): result = 0x00000104 E (667) wl_flash: init(161): result = 0x00000104 E (667) wl_ext_safe: init(73): result = 0x00000104 E (667) wear_levellin...
- Sun Sep 24, 2017 4:20 pm
- Forum: ESP-IDF
- Topic: Status of NVS encryption
- Replies: 0
- Views: 3835
Status of NVS encryption
I'm looking for some clarification on the status of NVS encryption. The docs specify: NVS is compatible with the ESP32 flash encryption system, and it can store key-value pairs in an encrypted form. Some metadata, like page state and write/erase flags of individual entries can not be encrypted as th...
- Thu Sep 14, 2017 5:48 pm
- Forum: ESP-IDF
- Topic: Control of Wifi transmitter duty cycle
- Replies: 0
- Views: 3757
Control of Wifi transmitter duty cycle
Our product will be undergoing EMC testing. The testing involves transmitting from the wireless radio on different combinations of protocols and channels. They require however that we use a 98% duty cycle during all testing. Is there a way to control this from the IDF, or am I misunderstanding what ...
- Tue Sep 12, 2017 7:22 pm
- Forum: General Discussion
- Topic: Not able to enable Secure Boot
- Replies: 6
- Views: 10315
Re: Not able to enable Secure Boot
I may have some idea why I'm getting the 'invalid magic number' in the partition table. When compiling the bootloader with secure boot enabled, the resulting binary is 30KB. However, the default offsets for the bootloader (0x1000) and the partition table (0x8000) only leaves ~28KB for the bootloader...
- Tue Sep 12, 2017 6:56 pm
- Forum: General Discussion
- Topic: Not able to enable Secure Boot
- Replies: 6
- Views: 10315
Re: Not able to enable Secure Boot
Thanks Angus, I'm just getting back around to looking into this again. I've updated the IDF to the latest---I'll report back with the results. I double-checked the IDF version. I did have the latest version in my last post, however we have a fork of the IDF for integration with our internal build to...
- Sat Aug 26, 2017 5:12 pm
- Forum: General Discussion
- Topic: Not able to enable Secure Boot
- Replies: 6
- Views: 10315
Re: Not able to enable Secure Boot
I've gotten the same error while using one-time-flash secure boot as well. I was going to post a separate thread about it until I saw this in a search. My output: I (785) boot: Checking secure boot... I (825) esp_image: segment 0: paddr=0x00001020 vaddr=0x3fff0010 size=0x00004 ( 4) I (905) esp_image...