gnupic: ccsc and gpsim - serial success!
Subject:
ccsc and gpsim - serial success!
From:
bill sack ####@####.####
Date:
14 Mar 2006 18:15:43 +0000
Message-Id: <44170852.1040302@buffalo.edu>
after hours of frustration and sore wrists, i've learned something that
may help someone with even less of a clue than I:
when i tried my homebrew (CCS->.hex) files with the new usart_gui, i
obtained only partial joy - i could type something into the USART window
and cause something to happen in the simulated pic, but it could not
talk to me. i noticed that on the gpsim breadboard my tx and rx pins
were both active (i.e.: red), but were both conf'd as inputs (i.e.:
pointing 'into' the pic). i had assumed that CCSC took care of conf'ing
the port c output pins correctly when it sets up the onboard rs232, and
as far as actually burning a pic and using it in a circuit, that's true.
I took a chance and used the CCSC port setup routine for port c to make
sure my tx (c6) and rx (c7) were set up correctly, i.e.:
SET_TRIS_C(0b00000010);
and now the (simulated) pic can listen and talk! wow! of course, i may
have broken something in the real world, time will tell.
>try a "load s" instead of "load c". This still confuses me too, but the
>'s' stands for symbol files and the 'c' stands for command files. However,
>symbol file extensions begin with 'c' (.cod) and command file extensions
>begin with s (.stc).
>
yes, sorry. i know this and yet get bitten by it again and again. in
this case though, i think the .cod files created by CCSC are of a very
different format (i can't tell by comparing, as they're binary files). i
was just curious to see if anyone knew of what the difference is or any
other way to load the .lst file made by ccsc into the source browser. it
might be a helpful step toward learning assembler (who am i kidding?).
**gpsim> load s blink-876.cod
an appropriate list file for blink-876.cod was not found
thanks scott and all for the great, great tools!
bill
