JALPIC One development board is alive

63 views
Skip to first unread message

Rob Jansen

unread,
Mar 26, 2019, 2:10:33 PM3/26/19
to jallib

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

Matthew Schinkel

unread,
Mar 26, 2019, 4:24:28 PM3/26/19
to jallib
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.

Rob CJ

unread,
Mar 27, 2019, 12:15:19 PM3/27/19
to Matthew Schinkel, jal...@googlegroups.com
Hi Matt,

No there is not bootloader required. It just programs the chip like your programmer does so it works fine on any new chip that has never been programmed. I attached the schematic but I will upload all info on GitHub once I completed the documentation.

I know about the video needed to be watched sideways. It was just to quickly share it. I will remove it after some time.

You mentioned the 'project' folder under jallib/jallib but this is something completely different than a software project. Do you not think that it will be better to add an extra repository in GitHub under Jallib called 'jalv2board' just like jalv2compiler? It might be that in the future other boards will also be developed. That is why I also proposed to a directory under jalv2board/jalpic_one for this board. Agree?

Kind regards,

Rob




Van: jal...@googlegroups.com <jal...@googlegroups.com> namens Matthew Schinkel <mattsc...@hotmail.com>
Verzonden: dinsdag 26 maart 2019 21:24
Aan: jallib
Onderwerp: [jallib] Re: JALPIC One development board is alive
 
--
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 jallib+un...@googlegroups.com.
To post to this group, send email to jal...@googlegroups.com.
Visit this group at https://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.
jalpic_one_schematic.pdf

Rob Jansen

unread,
Mar 27, 2019, 1:42:28 PM3/27/19
to jallib
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.

Bill Beek

unread,
May 20, 2021, 12:39:14 PM5/20/21
to jallib
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.

Rob CJ

unread,
May 20, 2021, 12:45:30 PM5/20/21
to jal...@googlegroups.com
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: jal...@googlegroups.com <jal...@googlegroups.com> namens Bill Beek <bill...@gmail.com>
Verzonden: donderdag 20 mei 2021 16:05
Aan: jallib <jal...@googlegroups.com>

Onderwerp: [jallib] Re: JALPIC One development board is alive
--
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 jallib+un...@googlegroups.com.

Rob CJ

unread,
May 20, 2021, 2:51:52 PM5/20/21
to jal...@googlegroups.com
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: jal...@googlegroups.com <jal...@googlegroups.com> namens Rob CJ <rob...@hotmail.com>
Verzonden: donderdag 20 mei 2021 18:45
Aan: jal...@googlegroups.com <jal...@googlegroups.com>
Onderwerp: Re: [jallib] Re: JALPIC One development board is alive
 

Bill Beek

unread,
May 21, 2021, 9:11:15 AM5/21/21
to jallib
Thank you Rob, i changed the code but now i get out of data space error in line 608:
This happens with the original files too.
I wonder what's wrong.

jal jalv25r5 (compiled Apr  3 2021)
generating p-code
3950 tokens, 358835 chars; 9015 lines; 16 files
generating PIC code pass 1
D:\JALone\project\jalpic_one\source\16f1455_jalpic_one.jal:
608: error: Out of data space!
writing result
1 errors, 0 warnings

It seems that the PIC is to small ??
kind regards Bill

Rob CJ

unread,
May 21, 2021, 12:56:10 PM5/21/21
to jal...@googlegroups.com
Hi Bill,

I compiled the sources too but do not get your result. I compiled the sources from the Jallib release with the fix I reported yesterday and got this result.

c:\jallib\compiler\jalv2_64.exe d:\PIC\Projects\2019\JALPIC_One\16f1455_jalpic_one.jal -s c:\jallib\lib <

jal jalv25r5 (compiled Apr  5 2021)
generating p-code
3950 tokens, 358777 chars; 9015 lines; 16 files
generating PIC code pass 1
generating PIC code pass 2
874 branches checked, 0 errors      
2583 data accesses checked, 0 errors
561 skips checked, 0 errors
writing result
Code area: 7738 of 8192 used (words)
Data area: 772 of 1024 used
Software stack available: 48 bytes
Hardware stack depth 7 of 16
0 errors, 0 warnings

I noticed  the following:  If you compile the program without the optimization to reduce variables you will run out of data space. 

Even with this statement in the program: pragma opt variable_reduce yes but disabling the optimization in e.g. JALEdit (I currently use Visual Studio code so that's why it did not happen for me) you will run out of dataspace. So if you are using JALEdit please check if the following checkbox is not checked.



Kind regards,

Rob


Verzonden: vrijdag 21 mei 2021 15:11
Aan: jallib <jal...@googlegroups.com>

Bill Beek

unread,
May 21, 2021, 1:27:35 PM5/21/21
to jallib
Hi Rob, your last post solved the problem, now i am able to compile without any errors.

Thank you very much for your advice, and keep going on with the good job for the PIC users.
Kind regards, Bill.
Reply all
Reply to author
Forward
0 new messages