I’m writing some code to allow my Photons to update firmware over TFTP from a local server, but when I build, I get errors like: ../../../build/target/user/platform-6-m/applications/kjolerom//libuser.a(tftp.o): In function `tftp_update(IPAddress, char*)': …/photon/firmware/user/applications/foo/tft…

As in, reordering the arguments? Makes no difference to make, no.

You are building APP=foo but there is an error about applications/kjolerom//. Have you added any additional references to the make file besides the ones added via the APP= parameter?

Sorry, the app is actually called kjolerom (“cooling room”, which is where this will be used), so s/foo/kjolerom/ in what I wrote, if you like. Make runs (I run it from firmware/main, but it doesn’t seem to make a difference if I build the system firmware too): $ make PLATFORM=photon APP=kjolerom …

@tfheen , do you have #include "system_update.h" in tftp.h? Not sure it will fix the problem but worth trying! :wink:

Yes, else it’d have stopped a lot earlier. This is a linking problem, not a compilation problem.

Tha’s a great question and one that’s not come up before. These functions aren’t currently exported from the system dynamic library. I can add them on the 0.4.9 release which will be released early next week. If you’re in a hurry and you wanted to do this yourself, you can compile the system mod…

Much appreciated! That got it compiling. Of course, I ended up with a red flashing LED, so now to find the bug in my code… :smile:

Ok, got a fair bit farther. I can now flash without crashing, but it seems like Spark_Prepare_For_Firmware_Update puts the firmware in a different location than it goes when I flash using dfu-util. (0x80c0000 is the address HAL_OTA_FlashAddress seems to return, dfu-util flashes to 0x80a0000). I trie…

The files themselves include a module_info struct that describes where in memory the file should be stored, so set the address to 0 and the target as FIRMWARE. Double check that you have crc32 in your path it’s used when building the file - the crc32 value is appended to the end of the file and use…

First 16 octets are: 0000 0a08 0815 0a08 0000 0300 0600 0501 My understanding is this translates to something like struct module_info_t { .module_start_address = 0x080a0000; .module_end_address = 0x080a1508; .reserved = 0; .reserved2 = 0; .module_version = 0x0003; .platfor…

How to get access to firmware flashing functions?

Troubleshooting

ScruffR December 6, 2016, 8:52am 17

Double posting is not appreciated:
I've answered your parallel question here

Topic		Replies	Views
Read Firmware from SD card and flash to P1 or Photon Firmware photon	20	1572	February 14, 2020
Using OpenLog to update Particle Firmware General photon	8	1336	February 24, 2019
Writing core firmware to external flash Firmware	30	6476	July 9, 2015
Port BCM43438(WiFi+BLE) to Photon Firmware	33	10186	April 11, 2018
OTA over HTTP working example! Troubleshooting boron	16	3003	April 8, 2020

How to get access to firmware flashing functions?

Related topics