Hi, everyone, I don't know if anyone here is working with PIC micros, but I am working on several projects, which I wanted to move the PIKLAB and SDCC with the GPSIM simulator.
So far I have gotten PIKLAB to load and apparently work with SDCC, but gpsim is fighting me tooth and nail. I cannot get it integrated with PIKLAB the way I expected.
So far I have added the following to my F11 system:
gpsim gpsim-devel gtk+* packages to get the basics of gtk+ and the extended packs PIKLAB of course SDCC SDCC-devel KDEbase (although I run Gnome) Ktechlab (needed to get some bits of gpsim I discovered in a web crawl) gputil
I can compile programs, but so far gpsim doesn't recognize the processor. This is as of today after adding KDEbase.
gpsim seems to run OK, but doesn't find some of its require fonts, or any of the processor files either. I tried invoking gpsim with gpsim -pp16f887 FreqCounter.hex (my file) but it couldn't find the processor or fonts. I am sure I can eventually sort out the fonts, but the other stuff is more perplexing. The packages were loaded from the system->Administration->Add/Remove software operation. Here is the message sequence from the command line invocation: $: gpsim -pp16f887 FreqCounter.asm
gpsim - the GNUPIC simulator version: Release 0.23.0
type help for help **gpsim> SimulationMode:114 The font "Courier Roman 14" does not support all the required character sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8;LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=en_US.UTF-8" (Missing character set "ISO8859-1") (Missing character set "ISO8859-1") (Missing character set "ISO8859-2") (Missing character set "ISO8859-3") (Missing character set "ISO8859-4") (Missing character set "ISO8859-5") (Missing character set "KOI8-R") (Missing character set "ISO8859-7") (Missing character set "ISO8859-9") (Missing character set "ISO8859-13") (Missing character set "ISO8859-14") (Missing character set "ISO8859-15") (Missing character set "JISX0208.1983-0") (Missing character set "KSC5601.1987-0") (Missing character set "GB2312.1980-0") (Missing character set "JISX0201.1976-0") (Missing character set "ISO10646-1") The font "Courier Bold 14" does not support all the required character sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8;LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=en_US.UTF-8" (Missing character set "ISO8859-1") (Missing character set "ISO8859-1") (Missing character set "ISO8859-2") (Missing character set "ISO8859-3") (Missing character set "ISO8859-4") (Missing character set "ISO8859-5") (Missing character set "KOI8-R") (Missing character set "ISO8859-7") (Missing character set "ISO8859-9") (Missing character set "ISO8859-13") (Missing character set "ISO8859-14") (Missing character set "ISO8859-15") (Missing character set "JISX0208.1983-0") (Missing character set "KSC5601.1987-0") (Missing character set "GB2312.1980-0") (Missing character set "JISX0201.1976-0") (Missing character set "ISO10646-1") The font "Courier Bold 14" does not support all the required character sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8;LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=en_US.UTF-8" (Missing character set "ISO8859-1") (Missing character set "ISO8859-1") (Missing character set "ISO8859-2") (Missing character set "ISO8859-3") (Missing character set "ISO8859-4") (Missing character set "ISO8859-5") (Missing character set "KOI8-R") (Missing character set "ISO8859-7") (Missing character set "ISO8859-9") (Missing character set "ISO8859-13") (Missing character set "ISO8859-14") (Missing character set "ISO8859-15") (Missing character set "JISX0208.1983-0") (Missing character set "KSC5601.1987-0") (Missing character set "GB2312.1980-0") (Missing character set "JISX0201.1976-0") (Missing character set "ISO10646-1") Unable to find processor cmd_load::load hex file FreqCounter.asm cmd_load:: load hex, Processor not defined **gpsim>
I tried to figure out where gpsim figures out its processors, and it seems that the processors are loaded as a shared object file ".so" from the gpsim-devel package. I have not yet been successful in discovering where that package is currently located on my system. I tried a "find . gp*.so -print" from the root directory, but had no success.
So my questions: 1. how should I proceed to discover any or all of the following: A. shared object file name B. install paths C. errors being generated if they don's show up in the gpsim windows (clearly the cause of not quoting error messages here other than the one that gpsim couldn't find the processor which appears in two different forms depending on how I invoke it). 2. A process to get gpsim working on Fedora (this seems to be a F11 issue because I have had little luck finding solutions on the web despite working on this for weeks.) 3. Once past 1 and 2, integrating the works for F11.
Maybe I can get some of you interested in neat microcontroller programming. These little mcpus are really quite powerful and neat for all kinds of jobs.
Thanks for any and all help, Les H
Les wrote:
So my questions:
- how should I proceed to discover any or all of the following: A. shared object file name
update your file location database with "updatedb". when prompt returns, try "locate gpsim|grep .so" for gpsim. change gpsim for other progs to find their .so files.
or from next "rpm -a -l gpsim|grep .so". change gpsim for other progs to find their .so files.
B. install paths
"rpm -q -l gpsim"
C. errors being generated if they don's show up in the gpsim windows
as root or "su -", "grep gpsim /var/log/*"
(clearly the cause of not quoting error messages here other than the one that gpsim couldn't find the processor which appears in two different forms depending on how I invoke it).
- A process to get gpsim working on Fedora (this seems to be a F11
go ahead and upgrade to f12, then work out any problems.
also, join fel list for cad/eda help.
Maybe I can get some of you interested in neat microcontroller
already am and i am an al bigot. do not like cc++ for talking to micro cpu's.
i am using al from z80 and z8 days, and i still see no reason to change.
due to trashing from a finial update of f11 and then trashing, crashing and wrecking when running auto upgrade to f12 and losing superblock on 3 drives, i am now almost restored to f12.
after i clear up a few more problems with last kernel update, i hope to get cad/eda working again and back to sweet life of design work.
g wrote:
Les wrote:
So my questions:
in addition, i was not for sure if i had 'gpsim' installed yet, so first boot this morning was to f12 and i do have it installed.
ran 'gpsim' from a terminal window to see what would happen and it came up ok.
that is until i open up additional windows from 'gpsim' gui and i got same errors as you did.
i did run 'locate' and 'rpm' as i mentioned and files are installed, they are just not linking in for some reason or other.
i do not have my email files rebuilt past last month as of yet, but i did run a search thru november and december and there is nothing related to 'gpsim'.
so, pull up page;
https://www.redhat.com/mailman/listinfo/fedora-electronic-lab-list
to get yourself subscribed so you can post the problem.
later.
On Sun, 27 Dec 2009 15:19:57 +0000 g wrote:
i did run 'locate' and 'rpm' as i mentioned and files are installed, they are just not linking in for some reason or other.
That sounds like an ldconfig problem. The dynamic linker will only search for libraries in places ldconfig has been told about (or you can explicitly set LD_LOAD_PATH environment variable).
Tom Horsley wrote:
On Sun, 27 Dec 2009 15:19:57 +0000 g wrote:
i did run 'locate' and 'rpm' as i mentioned and files are installed, they are just not linking in for some reason or other.
That sounds like an ldconfig problem. The dynamic linker will only search for libraries in places ldconfig has been told about (or you can explicitly set LD_LOAD_PATH environment variable).
now that you mention it, something does sound familiar about 'ldconfig', but it has been too long to have recalled just why of problem.
being that problem is in both les's and my install, it is something chitlish and rest of 'fel' crew need to correct.
it is possible that it has already been addressed, but my emails do not go back far enough yet for me to search for it.
google's database would be a good place to search if they had better functioning of boolean searching.
another place page les should look from is;
https://fedorahosted.org/fedora-electronic-lab/
'fel' crew have been working to have things grow from there, so les can run further checking to see if any bugs have been reported the linking problem.
thanks for your reply.
On Sun, Dec 27, 2009 at 6:05 PM, g wrote:
another place page les should look from is;
https://fedorahosted.org/fedora-electronic-lab/
'fel' crew have been working to have things grow from there, so les can run further checking to see if any bugs have been reported the linking problem.
Hello there,
Yes the Fedora Electronic Lab mailing list might be helpful for you.
sdcc has its binaries in /usr/libexec/sdcc in order not to create conflicts with other general software.
can you create a file "/etc/profile.d/mypiklab.sh" and add the following contents #-------- export PATH=$PATH:/usr/libexec/sdcc #------
Then reboot and try piklab again. If you still have issues with it, please post an example (on FEL's mailing list) so that we can reproduce this error.
also, since you are interested in microcontroller programming, do check: * gnusim8085 * gsim85 * avra * mcu8081ide
Examples can be found with
rpm -qd SOFTWARE
PS: I'll be offline in the month of January. https://fedoraproject.org/wiki/Vacation Please post your FEL related issues on FEL's mailing list.
Chitlesh GOORAH wrote:
On Sun, Dec 27, 2009 at 6:05 PM, g wrote:
Yes the Fedora Electronic Lab mailing list might be helpful for you.
i am already on list. i imagine that "Les hlhowell@pacbell.net" will soon be joining, as well as any members on this list that are interested in micro controllers.
from comments you have made in fel list, i felt that you followed this list also and would soon hear form you. glad you did not disappoint me. :)
sdcc has its binaries in /usr/libexec/sdcc in order not to create conflicts with other general software.
can you create a file "/etc/profile.d/mypiklab.sh" and add the following contents #-------- export PATH=$PATH:/usr/libexec/sdcc #------
can, and will.
Then reboot and try piklab again. If you still have issues with it, please post an example (on FEL's mailing list) so that we can reproduce this error.
will do tonight and post results to fel tsl.
also, since you are interested in microcontroller programming, do check:
- gnusim8085
- gsim85
- avra
- mcu8081ide
i had many of the fel additions, above included, tho not all check out yet, in fel f8 and f11, but do to 'auto upgrade' crashing and trashing system beyond practical recovery, i am currently rebuilding under f12.
PS: I'll be offline in the month of January. https://fedoraproject.org/wiki/Vacation
enjoy your vacation.
Please post your FEL related issues on FEL's mailing list.
when i find them, i will. fel tsl has help in keeping them to a minimum.
later, chit.
Hi, all, Thanks to Tom, Chit, and g. I have to go get my Christmas lights down and stowed, clean up some place for relatives to stay, and then I'll get back on this. I didn't even thing to look for another mailing list, DUHHH!!!
I'll try all the hints, gather more information and subscribe to the FEL list as soon as my melons (honey dos) are complete. For the non-americans, honeydew is a delicious melon. The pun is that wives give us a list of things to do, Honey, do this please?
Regards, Les H On Mon, 2009-12-28 at 04:04 +0000, g wrote:
Chitlesh GOORAH wrote:
On Sun, Dec 27, 2009 at 6:05 PM, g wrote:
Yes the Fedora Electronic Lab mailing list might be helpful for you.
i am already on list. i imagine that "Les hlhowell@pacbell.net" will soon be joining, as well as any members on this list that are interested in micro controllers.
from comments you have made in fel list, i felt that you followed this list also and would soon hear form you. glad you did not disappoint me. :)
sdcc has its binaries in /usr/libexec/sdcc in order not to create conflicts with other general software.
can you create a file "/etc/profile.d/mypiklab.sh" and add the following contents #-------- export PATH=$PATH:/usr/libexec/sdcc #------
can, and will.
Then reboot and try piklab again. If you still have issues with it, please post an example (on FEL's mailing list) so that we can reproduce this error.
will do tonight and post results to fel tsl.
also, since you are interested in microcontroller programming, do check:
- gnusim8085
- gsim85
- avra
- mcu8081ide
i had many of the fel additions, above included, tho not all check out yet, in fel f8 and f11, but do to 'auto upgrade' crashing and trashing system beyond practical recovery, i am currently rebuilding under f12.
PS: I'll be offline in the month of January. https://fedoraproject.org/wiki/Vacation
enjoy your vacation.
Please post your FEL related issues on FEL's mailing list.
when i find them, i will. fel tsl has help in keeping them to a minimum.
later, chit.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Chitlesh GOORAH wrote:
can you create a file "/etc/profile.d/mypiklab.sh" and add the following contents #-------- export PATH=$PATH:/usr/libexec/sdcc #------
Then reboot and try piklab again. If you still have issues with it, please post an example (on FEL's mailing list) so that we can reproduce this error.
i did and it *did not work*.
i guess "Les hlhowell@pacbell.net" does not have his Christmas lights down yet, so i will go ahead with a follow up post to fel tsl.
anyone interested in cad and eda and following thread, subscribe via;
https://www.redhat.com/mailman/listinfo/fedora-electronic-lab-list
later.
Hi, Chitlesh, I have attempted to reply to the thread that you and g created in the fel mailing list, but was unsuccessful. Once I get this worked out, it will tell you how I am setup, and what my goals are.
Regards, Les H On Tue, 2009-12-29 at 05:51 +0000, g wrote:
Chitlesh GOORAH wrote:
can you create a file "/etc/profile.d/mypiklab.sh" and add the following contents #-------- export PATH=$PATH:/usr/libexec/sdcc #------
Then reboot and try piklab again. If you still have issues with it, please post an example (on FEL's mailing list) so that we can reproduce this error.
i did and it *did not work*.
i guess "Les hlhowell@pacbell.net" does not have his Christmas lights down yet, so i will go ahead with a follow up post to fel tsl.
anyone interested in cad and eda and following thread, subscribe via;
https://www.redhat.com/mailman/listinfo/fedora-electronic-lab-list
later.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
-
Chitlesh GOORAH -
g -
Howard Howell -
Tom Horsley