Hi Bill,

I did a recompile and I ran into the same issue. Strange since I compiled 
everything before I uploaded it.

I found the following problem (still do not understand why it is like this).

In the programmer.jal file at line 182 you find this:
procedure timer_interrupt is pragma interrupt()

This should of course be:
procedure timer_interrupt() is pragma interrupt

That fixes the problem. I will upload the fix to Github.

Kind regards,

Rob

________________________________
Van: [email protected] <[email protected]> namens Rob CJ 
<[email protected]>
Verzonden: donderdag 20 mei 2021 18:45
Aan: [email protected] <[email protected]>
Onderwerp: Re: [jallib] Re: JALPIC One development board is alive

Hi Bill,

Nice to see that this is being used.

If you change it for another PIC type you do know that the programming 
algorithm may be different for other PIC types?

You mentioned changing the  programmer code for that PIC so it looka as if you 
have forgotten something somewhere but I cannot determine that from this error 
message. Can you post the program you changed?

Thanks.

Kind regards,

Rob

________________________________
Van: [email protected] <[email protected]> namens Bill Beek 
<[email protected]>
Verzonden: donderdag 20 mei 2021 16:05
Aan: jallib <[email protected]>
Onderwerp: [jallib] Re: JALPIC One development board is alive

Hello Rob, I would like to recreate the jalpic-one with another PIC for example 
16F1788 or an 18F type of which I have a number in stock.
To this end I adapted the library programmer.jal to the desired PIC type. 
Unfortunately I get a number of errors when I compile the file 
16F1455jalpic_one.jal, ergo no hex file to program the 16F1455, see below 
messages:
jal jalv25r5 (compiled Apr 3 2021) generating p code programmer.jal:
182: 'end' expected (got '(') programmer.jal: 182: {procedure starts at 
programmer.jal:
182} programmer.jal: 182: unexpected token: "(" C: \ Jallib \ project \ 
jalpic_one \ source \ 16f1455_jalpic_one.jal:
167: "programmer_reset" not defined C: \ Jallib \ project \ jalpic_one \ source 
\ 16f1455_jalpic_one.jal:
167: 'end' expected (got 'programmer_reset') C: \ Jallib \ project \ jalpic_one 
\ source \ 16f1455_jalpic_one.jal:
167: {procedure starts at C: \ Jallib \ project \ jalpic_one \ source \ 
16f1455_jalpic_one.jal: 158} C: \ Jallib \ project \ jalpic_one \ source \ 
16f1455_jalpic_one.jal:
167: "programmer_reset" not defined C: \ Jallib \ project \ jalpic_one \ source 
\ 16f1455_jalpic_one.jal:
167: unexpected token: programmer_reset 8 errors, 0 warnings
Can you tell me what I'm doing wrong and help me fix it?
FYI, I am 76 years old, and sometimes forget things.

Thanks in advance for the effort and the nice piece of work, Bill.


On Wednesday, March 27, 2019 at 6:42:28 PM UTC+1 [email protected] wrote:
Hi all,

New post on Jallist (@Matt: I have sent the schematic diagram to you).

The PIC is programmed almost at maximum speed. It can even be a little bit 
faster since in the demo I erase both the flash and the EEPROM before 
programming but the latter was not required (saves 14 ms:-)).

Since the 90 degrees rotated video was too disturbing I posted a new version 
which is rotated and I removed the previous link so also the reactions are 
deleted (sorry for that). Note that it is just a quick video to give you an 
impression. I am working on finalizing all documentation of the board and how 
to use it.

Some other info. There are two PICs on this board, The first PIC is the 
controller PIC that does the USB handling, the command handling and the 
programming of the second PIC, the latter I call the application PIC. For the 
first PIC I used a PIC16F1455 and for the second PIC I used a PIC16F18857. The 
board is completely made of standard components so not using any Surface Mount 
Devices. This makes it easier to assemble.

The application PIC does not use a bootloader but is programmed just like you 
do with a PicKit 3 so you can use a new virgin PIC for the application PIC.

If you have more questions or requests let me know.


On Tuesday, March 26, 2019 at 9:24:28 PM UTC+1, Matthew Schinkel wrote:
Looks quite nice Rob, I like the quick programming. Is there any bootloader 
required for the PIC16F18857?

Where can I find the schematic?

It's hard to watch that video sideways.

Matt.

On Tuesday, March 26, 2019 at 2:10:33 PM UTC-4, Rob Jansen wrote:

Hi all,


Also posted on Jallib but here some more info.


I completed the hardware and the software for the JALPIC One development board. 
You can compare it with an Arduino Uno but now using a PIC and developed using 
JAL. The biggest advantage is that you can now test your programs on a board 
without the need of a programmer.


Instead of a thousand words, have a look at this short video that I made. Do 
not look to much at the quality, I made it to give you an impression of how it 
works and how it makes your life easy. You have to turn your head when watching 
since I wanted to have both the board and the program on the video.


https://youtu.be/Mq3YajeFGc0


I still need to add the connectors to the board but it seems to work fine. I am 
also in the process of documenting how you use the board and which commands it 
supports. After that my plan is to put all information: Schematic, board 
layout, control software, sample programs and documentation on GitHub in a new 
respository 'jalv2board'. I will also make a subdirectory jalpic_one since you 
never know if another version will be made with another PIC.


Suggestions are welcome of course.


Kind regards,

Rob

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/f17329cc-0d6a-4bf0-86f3-fd214127ae9dn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/f17329cc-0d6a-4bf0-86f3-fd214127ae9dn%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/AM0PR07MB624116FAB882C17D9DA2B989E62A9%40AM0PR07MB6241.eurprd07.prod.outlook.com<https://groups.google.com/d/msgid/jallib/AM0PR07MB624116FAB882C17D9DA2B989E62A9%40AM0PR07MB6241.eurprd07.prod.outlook.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/AM0PR07MB62413905FB7E2A6CD35558E8E62A9%40AM0PR07MB6241.eurprd07.prod.outlook.com.

Reply via email to