This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Bug in Bluetooth Hardware Evaluation Tool v1.0 converting .bts to .h

I noticed a bug when using the Bluetooth Hardware Evaluation Tool v1.0 to convert a service pack from .bts format to .h format.  The .h file produced has incorrect new lines near the beginning and the end of the .h output file.

Nomenclature:

<CR> = Carriage Return character = 0x0D

<LF> = Line Feed character = 0x0A

Newline = a line terminator, usually the combination <CR> followed by <LF>, or sometimes only <CR> or only <LF>, but never the sequence <LF><CR>.

BUG:

The first 2 newlines and the last 2 newlines in the .h output file file are <LF><CR> instead of <CR><LF>.  The remaining lines are correctly terminated by <CR><LF>.  The incorrect newlines for the first 2 and last 2 lines in the file cause the file to be unviewable in some editors such as Notepad.  I used a hex editor to manually reverse the incorrect newlines.

Is this the correct place to post this bug report?