Jal Developers, Can any of you tell me what the calling vectors are used for? In treerep.c there is the 'chip_with_call_vectors' macro. Are call vectors used ...
Hi Brian, "vectors" in JAL means that all CALL entry labels are placed at first in page_0 (and then set the correct page for jump) in this way: ORG 0000...
Just curious, nothing important, in the code below, "data_booter" should be included, but is not. I even believe that in previous compiler versions include was...
Ok again me, with another stupid question ;-) Is procedure nesting allowed ? I cann't find anything in the manual, so I guess YES. The compiler doesn't...
Stef, I know that you write this too late at night and I'm reading it too early at morning. ;) Please, be more explicit. Regards, Javi. www.japus.org...
... definitely ... can you show a (small) weirdly-behaving program? Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische...
hi Javi, it works, but different from what I expected ;-) Now I had to reproduce the problem, I discovered another (interesting) phenomen Look at the var AAP, ...
... Hi Stef The if-statement is a statement, not a compiler directive. And both the then-part and the else-part are separate scopes (nested within the ...
hi Wouter, Javi, As always it didn't work in a small program, so I had to strip the large program down. But below is the minimal program . After a reset the...
... Well here is a collection of all the "fancy" files, used in this example but I don't think it has anything to do with the fancyness ;-). So maybe it's...
hi guys, as I ran into another weird problem (changed too many things at once) So I started my simulator and solved that one. So I decided to ran the procedure...
I ran into a "code too large" error when exceeding 2K of code on a 16F88 (a 4K part). So I went ahead and changed target_last_rom to 0xFFF, and all seems OK,...
hi Tim, ... Is this a "pragma" statement ? And if is is there also a pragma to change the data-romsize ? (I like to use target=628 for all my pics, because of...
... No, the change was made in the compiler source code. For the 16F88, It's line 1306 in parser.c for 0.4.60. ... That can be changed in source code as well,...
Hi all I have made some modest progress and JPIC14 is now reduced to port and pin handling only :-) The rest is in PIC-specific files. (Only '877 for now) ...
Hi Eur, ... Interrupts should be disabled during eeprom write "magic sequence", seems that this is done by brute force. You can find a better interrupt ...
hi Eur, ... I just tried it on one port, but the results were poor :-( My estimation for each port: -1 valuable bank-0-RAM space ;-) +50 code space :-( ...
What about naming ?? Are you planning official Microchip names, Wouter's name or .... PORTA or PORT_A etc. TMR1L or f877_tmr1l etc. C or status_C etc. GIE...
... If I may drop in: If you arrange to have different definitions for the different chip by all means use the Microchip names for the registers. Choose...
... I haven't touched the ports yet, but PORT_A is included at the right address. That should be PORTA, right? ... Definitely TMR1L, on all PICs That may be a...
... As far as I have to say anything: "please do !!!" (sorry Wouter, I don't have anything against your name/names/naming, but it's so terrible confusing ;-) ...
... Both seems a good idea. But then you must be consequent and add "C" too. You know that JAL can handle very well "asm bcf C" without specifying where...
On Fri, 01 Oct 2004 00:54:06 +0200, Stef Mientki <s.mientki@...> ... OK. This is in line with the datasheet. All bits have a unique short notation. ...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
