Newbie question
 
Notifications
Clear all

Newbie question

4 Posts
3 Users
0 Reactions
2,700 Views
Posts: 9
Topic starter
(@rslaback)
Active Member
Joined: 14 years ago
[#28372]

Some of you may know that I am attempting to take my students through the process of creating a Renard SS16, programming the chips and running a show on our school building. Before this experience my PIC knowledge was limited to taking them off and on the baords inside my old school arcade game to get a better connection if the game would freeze.

We picked up some K150 Programmers which I (now) know aren't the greatest. Long story short we reprogrammed all the PICs from our group buy with the diagnostic firmware since those actually made the LED's come on which the kids mistook for a boot sequence.

I'm now downloading the MPLAB tools to compile the hex file for the operational firmware so we can get our boards working.

Here are my questions: Do all programmers use the same hex file regardless of the programmer model itself? If so, why isn't the hex file shared in the wiki instead of the asm, essentially eliminating a step people like me who just want it to function but aren't necessarily interested in tweaking the original code?


3 Replies
dirknerkle
Posts: 10309
(@dirknerkle)
Illustrious Member
Joined: 18 years ago

There are some sets of HEX files in the FILE library -- for example, PWM firmware for 57600 baud and start addresses from 0-34 in one zip file. There are others, too.

But the real reason they're all not available is because some people want to use a different baud rate, which has to be compiled into the HEX. Some people want to use PWM while others may not. That has to be compiled into the HEX. Some want a DC build (for DC lights only, not AC) and that is a setting that has to be compiled into the HEX. Others want to tweak a few of the other settings, such as changing the polarity of the output pins from - to +. Yep, you guessed it -- has to be compiled into the HEX.

So the problem is that there are many options, combinations and permutations of settings inside the firmware that are changed in the ASM file and then compiled into the HEX.

And that's the reason why there's not just "one" HEX file.


Reply
Wayne J
Posts: 7789
(@wayne-j)
Illustrious Member
Joined: 19 years ago

In the past shared .hex files seemed to get corrupted when downloaded, so using the .asm file was/is a more reliable way. I made a step by step video for PIC programming to make things easier to understand. Knowing how to do this gives folks the knowledge to make configuration changes when they decide they want/need to, so it seemed as a better way.

But... if you want the .hex, here ya go. 🙂


Reply
Posts: 9
Topic starter
(@rslaback)
Active Member
Joined: 14 years ago

Makes perfect sense.


Reply
Share: