These are chat archives for SmingHub/Sming
There are some things that I need to figure out:
path=/upload host === 10.0.0.210 parsed Request: GET, nodata TCP received: 327 bytes onReadyToSendData: 1 response sendHeader response sendBody Stream completed TCP connection closing ~TCP connection -TCP connection onAccept state: 0 K=0 Free heap size=38568, K=0 +TCP connection timeout updating: 70 -> 90 TcpServer onClient: 10.0.0.219 path=/upload host === 10.0.0.210 multipart - boundary === ---------------------------191781408624973 content-type === multipart/form-data content-length === 5615 content-type === application/octet-stream parsed Request: POST, 5615 bytes NETWORK_MAX_HTTP_PARSING_LEN POST FAILED SEND ERROR PAGE TCP received: 1460 bytes onReadyToSendData: 1 TCP connection closing ~TCP connection -TCP connection onAccept state: 0 K=0 Free heap size=38568, K=0 +TCP connection timeout updating: 70 -> 90 TcpServer onClient: 10.0.0.219 TCP received: (null) TCP connection closing ~TCP connection -TCP connection
We should make the upload to a flash address which is given in the upload data, there is more that applications to upload. f.e. spiffs FS.
In my first idea of filename conventions i was thinking of !0x10000 but needs to revised, maybe request parameters ?
the preliminary interface allows for uploading both rom and spiffs at the same time or individually. Also it's possible to disable spiffs upload - at least that's what I thought.
I see some issues with providing the flash address via http query parameters - mostly if the user enters wrong data the upload will overwrite the wrong sectors and cause trouble. And I bet a lot of people will open issues afterward with "why is Firmware upload not working?".
I like the idea from rboot, to specify "rom slots" from which the program/user can select one
t sweat it with the design - its hard to communicate sometimes via chat and github