FW.SFE file disappears

Development Boards MicroMod
1

I just received my Logomatic v2. I carefully followed the instructions in “Part II: Compiling and Loading Code onto an USB Bootlader Enabled Board”. I successfully pasted the FW.SFE file on the Logomatic SD card but when I disconnected the USB cable, the program did not execute (i.e., the Red and Green LEDs did not flash). Then I turned off the Logomatic, reconnected the USB cable and turned it back on again. No FW.SFE file, or any othe file for that matter, on the SD card. I went through this process several times and the file is always missing.

I am compiling using WinARM 7. The only changes I make in the ARM Bootloader Tutorial Code (main.c) are to delete all references to the Blue LED (the Logomatic only as Red and Green) and change the delay from 333ms to 500ms.

Any ideas of what is wrong, how I can debug, or what the fix might be?

Thanks all.

2

Hi,

I am having exactly the same issue.

I am using the Package Tracker and also removed all reference to the Blue LED.

The time interval has been left at 333ms but again when I move the file over to the SD card it is apparantly loaded and removed from the SD card but all I get is a solid green LED and it doesnt continue to do anything more.

Is there something basic we are missing here?

Also where can I get hold of the original FW to reset it back to standard in the meantime?

Thanks for any help!

Oh and as an aside, when compiled my FW.SFE file is less than 1kb? is this correct? in the tutorial the image shows a 57kb file but I dont appear to be doing anything wrong - save code, make all, copy to sd card.

3

Hi,

if your FW.SFE has only a size 1kb something is wrong. Don’t know what. Are there any warnings when compiling the code?

I had the same problem with a disappering FW.SFE-file and not working bootloading.

My solutions:

a) Formating the SD-card before uploading

b) or uploading the FW twice: After the file disappears, I upload the same file again and afterwards the package tracker works.

I had the problems only with the “new” package tracker with adxl345 Accelerometer. The old one with the LIS302 doesn’t have this problem. I really do not unterstand why.