... 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. ...
... With a 'put procedure? That does take precedence over a variable with the same name, right? I agree with stef: messing with the ports in assembler is...
Hi all, Eur, I've some already done, I'll send you to your email box (not here because zip size is 1.2MB). [PS] Hope that you are familiar with perl. :) ...
... Yes, but IMHO it would be reasonable to give access to the unbuffered port in pure Jal too. For instance when all 8 bits are always used together the...
To optimize for speed, I often use pragma target chip 16F628 even when using 16F877. Now just passing the 2K boundery, I was thinking of using pragma target...
the compiler switch -ow should result in parameter passing through w. Does this wsitch still works ? (because I cann't see any difference :-( What I do see,...
some suggestions for tris flushing (I still am not able to remove shadowing efficiently :-( :-( My suggestions: 1: don't use "tris" instruction because it's...
What about naming in 12F675 / 12F629 ? The IO ports are called there GP or GPIO and tris is calles TRISIO. I solved this problem, by simpling adding PORTA and...
Hi Stef, I think that we must go to a specific "jpic" for each processor, not only with SFRs but also with Config, RAM, Flash, Eeprom, etc. Here's the "jal"...
hi Javi, ... I fully agree with you, Yes that's the way to go !! (but it doesn't solve the problems with the weird 12F675 naming) And if then pragma max_rom...
... It may not improve much in those respects, but it will improve the 'acceptance' (by the compiler and its users) of future - even many current - PICs...
Dear Jalians I'm putting together a project proposal for my school where I would include paying money to somebody to add features to JAL I'm looking at adding...
... hi Massimo, I like the idea very much. But as Wouter says, it's not cheap, and therefor economical very hard to achieve. (btw, before I forget, or you...
... Stef, I support this. Also see my post in jallist #16180 ... When i moved from 16F628A to 16F648A i made JAL (4.60) believe that the chip was a 16F877....
I was just experimenting with I2C on a 16f877 and after a bit of debugging I found that the I2C Jal libraries are using port A, pins 3 and 4 for the I2C. ...
