Facebook
Google
GitHub
Linkedin
Thank you for the feedback.
Help converting an "asm" file over to HEX for a PIC12F508 ic
- Thread starter Flash001USA
- Start date
-
- Tags
- convert asm to hex
John I upgraded to MPLAB ver 8.92 but I was unclear about "ASM v. 5.49" Is this a plugin for the program? I looked all over their website for this file and could not find it in the archives. The install went with zero errors and I did try my hand at the program following your steps but with no luck. Rather than trying to exolain the steps I did I took screenshots along with adding some text explaining what I did. Hopefully I just made a simple misstep and you will spot it. I am sorry for picking your brain but I know you will see my error and hopefully put me on course.
Attachments
The assembler is standard in MPLAB 8.x Photo 3 says it is working but you need to tweak the code.
Add the code shown in lines 4,5, and 6 below. The basic code doesn't expect the 12F508 so it doesn't know to include the file that has the processor register descriptions for the assembler.
You can just remove the 'list' lines. They are redundant here and will generate a Processor Mismatch error if not commented out or deleted.
Don't forget the manuals linked in #20.
It should assemble OK.
Add the code shown in lines 4,5, and 6 below. The basic code doesn't expect the 12F508 so it doesn't know to include the file that has the processor register descriptions for the assembler.
You can just remove the 'list' lines. They are redundant here and will generate a Processor Mismatch error if not commented out or deleted.
Don't forget the manuals linked in #20.
It should assemble OK.
Code:
; list p=12f508A ; <---- you don't need these, comment out with a semicolon or delete
; list p=12F509A
ifdef __12F508 ;<---- add these 3 lines - copy/paste to the source
include "p12F508.inc"
endif
ifdef __12C508A
include "p12c508a.inc"
endif
ifdef __12C509A
include "p12c509a.inc"
endif
Last edited:
Yes, one could go through the entire source code, find TIMEOUT, and figure out how to bypass it. It would probably be easier to do that and set to hours. Note TIMEOUT is defined as the product of 100 and 300 = 30,000 "clicks" of the clock in 0.01 seconds. The system clock runs at 4 MHz/4 = 1 MHz = 1 us per "tick." 30,000 us = 30 ms = 0.03 seconds. 5 minutes is 300 seconds. So somewhere in the code is a delay for a count of 10,000, or something like that.
Such long periods usually execute loops within loops, like this:
Code:
Source: http://www.piclist.com/techref/piclist/codegen/delay.htm
; Delay = 300 seconds
; Clock frequency = 4 MHz
; Actual delay = 300 seconds = 300000000 cycles
; Error = 0 %
cblock
d1
d2
d3
d4
endc
;299999995 cycles
movlw 0x54
movwf d1
movlw 0xA1
movwf d2
movlw 0xFD
movwf d3
movlw 0x02
movwf d4
Delay_0
decfsz d1, f
goto $+2
decfsz d2, f
goto $+2
decfsz d3, f
goto $+2
decfsz d4, f
goto Delay_0
;5 cycles
goto $+1
goto $+1
nopThe code you have needs to be looked at. Although will it will not need to be analyzed in detail, simply deleting a delay could cause problems. One needs to find the context for how the delay is called and deal with it there. Alternatively, if the delay code is something like the code posted just above, one could change the constants to make it run longer. The former approach might be better.
Re: ASM version
MPLab is a suite of programs and files. The ASM version that is incorporated in MPLab 8.92 is shown in release notes:
Perhaps it is not too hard, if you don't mind code with some broken parts. The sleep command seems to come from here:
The critical part is when it tests the timer+0 register bit<7> for being set (btfsc). When that bit gets set, it goes to the subroutine, "power_down." That opens a few options. Immediately upon going to that routine, you could go to "loop0, " which is probably the start. An alternative is to comment out the "goto poweer_down" like this:
That change will cause it to ignore "timer+". I don't know for sure what letting timer+ just keep running will do. Probably nothing.
Disclaimer: I am not responsible for any damages, physical and/or mental, including and not limited to consequential damages, for allowing this theremin to run continuously. In other words, for example, if your cats climb the walls and/or your wife divorces you, it's not my fault.
Code:
loop8 incf note,w ; silent ?
bnz main_loop ; branch if not
movlw SAMPLE1/d'10'
btfsc mode,0
movlw SAMPLE2/d'10'
subwf timer+1
skpc
decf timer+0
btfsc timer+0,7 ; sleep if timeout
goto power_down
goto loop0
Code:
movlw SAMPLE1/d'10'
btfsc mode,0
movlw SAMPLE2/d'10'
subwf timer+1
skpc
decf timer+0
; btfsc timer+0,7 ; sleep if timeout
; goto power_down
goto loop0Disclaimer: I am not responsible for any damages, physical and/or mental, including and not limited to consequential damages, for allowing this theremin to run continuously. In other words, for example, if your cats climb the walls and/or your wife divorces you, it's not my fault.
John here's an update: All is well with the code universe. I attached a few photos to explain what I did... It works!Perhaps it is not too hard, if you don't mind code with some broken parts. The sleep command seems to come from here:
The critical part is when it tests the timer+0 register bit<7> for being set (btfsc). When that bit gets set, it goes to the subroutine, "power_down." That opens a few options. Immediately upon going to that routine, you could go to "loop0, " which is probably the start. An alternative is to comment out the "goto poweer_down" like this:Code:loop8 incf note,w ; silent ? bnz main_loop ; branch if not movlw SAMPLE1/d'10' btfsc mode,0 movlw SAMPLE2/d'10' subwf timer+1 skpc decf timer+0 btfsc timer+0,7 ; sleep if timeout goto power_down goto loop0
That change will cause it to ignore "timer+". I don't know for sure what letting timer+ just keep running will do. Probably nothing.Code:movlw SAMPLE1/d'10' btfsc mode,0 movlw SAMPLE2/d'10' subwf timer+1 skpc decf timer+0 ; btfsc timer+0,7 ; sleep if timeout ; goto power_down goto loop0
Disclaimer: I am not responsible for any damages, physical and/or mental, including and not limited to consequential damages, for allowing this theremin to run continuously. In other words, for example, if your cats climb the walls and/or your wife divorces you, it's not my fault.
Attachments
Last edited:
BobaMosfet
- Joined Jul 1, 2009
- 2,211
Just for edification- An '.asm' file is an assembly language text file. In order to convert it to an OBJECT (hex) file, you need to run it through the Assembler that it was originally written with. An Assembler takes the text file, checks it's syntax, identifies all labels, addresses, pointers and so forth, builds a symbol table to hold all that, then calculates all addresses, relative, and direct and 'links' this altogether with a linker (adding stubs as necessary), and turns this into a binary file (object file) that can have a .obj or .hex extension for direct load into the processor/micro-controller for which it was originally intended to execute on.
Good luck in your journey.
Hey thank you for the reply. Yeah has been interesting for me to say the least. I was able to get in there and not only generate the hex file that I needed but I was also able to edit the ASM file to do exactly what I needed it to do. This is something I should have learned a long time ago but never did because my job was all hands on repairing and/or basic designing along with upgrading projects. Now that I'm retired I want to take it on for the fun and the challenge of learning this. I can't thank everybody enough who stepped up to point me in the right direction.
The chips you are using are two of the simplest Microchip offerings. If you decide to move on with 8-bit stuff, I suggest the enhanced midrange (e.g., 12F1840 and 16F1xxx ). I use the 16f1829 as default, but if I need more pins, I use another 16F1xxx. Sixteen bit core (18Fxxxx) and 16-bit chips (e.g., PIC24F) are a big step. You probably do not need them. We went to the moon with much less.
" We went to the moon with much less." That should be on a Tee-Shirt... lol!
How would I use this asm & Hex with a 16f84 chip insted of the 12C508A? would you send me instructions on that Thank you!
