{"action":"created","issue":{"url":"https://api.github.com/repos/nodemcu/nodemcu-firmware/issues/1479","repository_url":"https://api.github.com/repos/nodemcu/nodemcu-firmware","labels_url":"https://api.github.com/repos/nodemcu/nodemcu-firmware/issues/1479/labels{/name}","comments_url":"https://api.github.com/repos/nodemcu/nodemcu-firmware/issues/1479/comments","events_url":"https://api.github.com/repos/nodemcu/nodemcu-firmware/issues/1479/events","html_url":"https://github.com/nodemcu/nodemcu-firmware/issues/1479","id":173625607,"number":1479,"title":"spiffs image format failed when first boot","user":{"login":"kicer","id":3350203,"avatar_url":"https://avatars.githubusercontent.com/u/3350203?v=3","gravatar_id":"","url":"https://api.github.com/users/kicer","html_url":"https://github.com/kicer","followers_url":"https://api.github.com/users/kicer/followers","following_url":"https://api.github.com/users/kicer/following{/other_user}","gists_url":"https://api.github.com/users/kicer/gists{/gist_id}","starred_url":"https://api.github.com/users/kicer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kicer/subscriptions","organizations_url":"https://api.github.com/users/kicer/orgs","repos_url":"https://api.github.com/users/kicer/repos","events_url":"https://api.github.com/users/kicer/events{/privacy}","received_events_url":"https://api.github.com/users/kicer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-08-28T02:30:26Z","updated_at":"2016-08-29T03:20:23Z","closed_at":null,"body":"### Actual behavior\r\nI have enabled the `DEVELOP_VERSION` macro, then build and got the `0x90000-32mb.bin` file.\r\nAfter download firmware(nodemcu*.bin -> 0), then restart device, the log shown as follows:\r\n* fs.start is 0x90000 or 0xa0000 ?\r\n\r\n```\r\nsoftAP(1a:fe:34:cc:85:ec)\r\nadd if1\r\ndhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)\r\nbcn 100\r\n\r\n_flash_used_end:40283d7b\r\nfs.start:90000,max:36a000\r\nmount res: -10025, -10025\r\nFormatting file system. Please wait...\r\n_flash_used_end:40283d7b\r\nfs.start:a0000,max:35a000\r\nmount res: 0, 0\r\nFormatting: size 0x35a000, addr 0xa0000\r\n_flash_used_end:40283d7b\r\nfs.start:90000,max:36a000\r\nmount res: -10025, -10025\r\n\r\n*** ERROR ***: unable to format. FS might be compromised.\r\nIt is advised to re-flash the NodeMCU image.\r\nTask task_lua started.\r\n\r\nNodeMCU 1.5.4.1 build Aug 26 2016 powered by Lua 5.1.4 on SDK 1.5.4.1(39cb9a32)\r\nlua: cannot open init.lua\r\n> Heap size::33800.\r\n> =file.fscfg()\r\n589824\t3579904\r\n> \r\n=file.fsinfo()\r\nstdin:1: file system failed\r\nstack traceback:\r\n\t[C]: in function 'fsinfo'\r\n\tstdin:1: in main chunk\r\n> =file.format()\r\n_flash_used_end:40283d7b\r\nfs.start:a0000,max:35a000\r\nmount res: 0, 0\r\nFormatting: size 0x35a000, addr 0xa0000\r\n_flash_used_end:40283d7b\r\nfs.start:90000,max:36a000\r\nmount res: -10025, -10025\r\n\r\n*** ERROR ***: unable to format. FS might be compromised.\r\nIt is advised to re-flash the NodeMCU image.\r\nstdin:1: Failed to format file system\r\nstack traceback:\r\n\t[C]: in function 'format'\r\n\tstdin:1: in main chunk\r\n```\r\n### NodeMCU version\r\nmaster, but with some features add~\r\n\r\n### Hardware\r\nESP-12F module"},"comment":{"url":"https://api.github.com/repos/nodemcu/nodemcu-firmware/issues/comments/243023980","html_url":"https://github.com/nodemcu/nodemcu-firmware/issues/1479#issuecomment-243023980","issue_url":"https://api.github.com/repos/nodemcu/nodemcu-firmware/issues/1479","id":243023980,"user":{"login":"kicer","id":3350203,"avatar_url":"https://avatars.githubusercontent.com/u/3350203?v=3","gravatar_id":"","url":"https://api.github.com/users/kicer","html_url":"https://github.com/kicer","followers_url":"https://api.github.com/users/kicer/followers","following_url":"https://api.github.com/users/kicer/following{/other_user}","gists_url":"https://api.github.com/users/kicer/gists{/gist_id}","starred_url":"https://api.github.com/users/kicer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kicer/subscriptions","organizations_url":"https://api.github.com/users/kicer/orgs","repos_url":"https://api.github.com/users/kicer/repos","events_url":"https://api.github.com/users/kicer/events{/privacy}","received_events_url":"https://api.github.com/users/kicer/received_events","type":"User","site_admin":false},"created_at":"2016-08-29T03:20:23Z","updated_at":"2016-08-29T03:20:23Z","body":"I use `ESPFlashDownloadTool_v3.3.4` for download in win10, just select chip size is 32mb.\r\nThe module is ESP-12F that flash size is 4MB. refer the documents of spiffs,allowed flash a small image in 4MB chip. I just want to verify spiffs-image file is valid or not.\r\n\r\n> The disk image file is placed into the bin directory and it is named 0x<offset>-<size>.bin where the offset is the location where it should be flashed, and the size is the size of the flash part. It is quite valid (and quicker) to flash the 512k image into a 4M part. However, there will probably be limited space in the file system for creating new files.\r\n\r\nSeems when call the `file.format()`, `fs_start` is incorrect(0x90000->0xa0000)."}}
{"actor":{"display_login":"kicer"}}