How to specify device type and revision for application.dat file?

[la-ble]

I'm manually creating the .dat file for a DFU following the format specified in this document.

Where can I get the device type and revision values from to populate those first two words?

Does it make a difference whether I compress the folder containing application.dat and application.hex on a Mac vs Windows PC?

I've attached my application.dat and application.hex files for reference. The compiled hex is the example experimental_s110_with_dfu for the pca10028 dev board, but I still seem to be getting the error:

application.hex

application.dat

application.zip

[Stefan Birnir Sverrisson]

Hmm, I have recently done the same with good success. I followed the instructions in the same document to generate the CRC for the .dat file. Then renamed the the files to application.hex and application.dat and zipped them with 7-zip on my Windows 7 PC. I have not tried with MAC.

Have you tried this with other applications?

Are you willing to share you zip file?

[la-ble]

Yes. My zip file contains the attached application.hex and application.dat. I also just compressed it on a mac. Is my application.dat correct? I do NOT KNOW HOW to specify the first two words for my device (device type and revision). Will 0xffff and 0xffff fail? The contents of my .dat file are currently: ffff ffff ffff ffff 0100 feff 5a00 cf74

[la-ble]

I'm testing with the dfu example, but please provide another app example (e.g. a blinky) that I can use instead if you can. Can you attach a sample application.hex, application.dat, and application.zip that you know works?

[la-ble]

There was a mistake in how I read the documentation. The user CAN specify if desired a device type and revision. This is not something specified by Nordic. It is something the user can choose to use.

The particular error shown above was because I was using an experimental variant of the OTA DFU firmware examples.