.HEX file for programming

Only in uVision2 I know how to configure:

Select Target1 and right kick your mouse;
select "Options for target 'target1'";
Choose "Output" select card;
Tick "Create HEX file"

I don't know whether it is useful in uVision3, sorry

"I don't know whether it is useful in uVision3"

I'm pretty sure that uVision3 is identical in this respect.

Anyhow, you could always just use the 'Search' facility in Windows Explorer - if it's there, that'll find it!

Where can I find the .HEX file for programming after the building?

If you select "create hex file" option in the output tab, your hex file is in the same folder as your project.

Andy

"If you select 'create hex file' option in the output tab, your hex file is in the same folder as your project."

No - it goes in the same folder as the Objects

(However, the default folder for the objects is same folder as the project)

Of course, if you don't select 'create hex file', it will not create a hex file.

Perhaps you should look for .H86 files instead of .HEX ones.

Regards,
- mike

"Perhaps you should look for .H86 files instead of .HEX ones."

Hmmm... how did the "Toolset" come to change from C166 to C51?

C51 certainly generates .HEX by default; does C166 default to .H86?

does C166 default to .H86?

Mine certainly does. Moreover, I've never been able to find a setting to change that. When I had to, I renamed the file from .H86 to .HEX by hand. Of course, it can be done automatically with the 'Run User Program After Make' feature.

- mike

Yes, I have only .H86 file. I wonder why. Can this .H86 file be programmed into a microprocessor? Mike, you said you renamed the .H86 file into a .HEX file by hand, does this new .HEX file work? Should I input the DOS rename command in the 'Run User Program After Make' field?

Best Wishes

Which C16x device variant do you actually use?

Reinhard

Can this .H86 file be programmed into a microprocessor?

Yes, it can. It is the HEX file you want. If you don't like the .H86 extension, you can input the DOS rename command into the 'Run User Program After Make' field.
By the way, some ROM programmers don't like HEX files where data are not ordered, which is the case for Keil tools with default settings. You can instruct Keil tools to produce ordered HEX files by using the 'Flash fill byte' option, just set it to 0xFF.

Regards,
- mike

I need to elaborate on Mikes post:
By the way, some ROM programmers made by people that ignored the standard don't like HEX files where data are not ordered.

Caveat emptor You (often) get what you pay for.

Erik