How does everyone debug their code?

[mister_e]

If you have PICKIT there's no need for any RS232 level shifter, no resistor either... use the USART tool.

If you're a bit clever, you'll design your thingy to accept ICSP. And then you can also use those ICSP line for Debug with PICKIT.

That's an handy tool for less than 50$.

[tenaja]

I uses ISIS. It simulates the code right on the computer, complete with SPICE for the electrical schematic. With PBP, I've got to watch the compiler asm output, but I can see all of the variables change and i/o pins as fast as I want, with breakpoints. When I use Proton+, I get to step through the basic code, one basic line at a time. It even gives me the option to see the assembled code between each basic line, and step through that, too.

[HankMcSpank]

Well, I've after two solid nights battling to get my PIC 16F690 to talk to the outside world...I've got it working

I decided I really did want some form of serout command (that I could call on demand), therefore last night I messed about with a MAX232 for a couple of hours....no success (I now realise that this was becuase I was feeding the MAX232 just 3V...sourced from the PICKIT2 VCC - it needs 5V - doh! Thanks to DavyJones for emailing me the schematics)

Anyway, the post that mister_e madecaught my attention - & I've ended up going that route. I now have PIC program going outputing to the UART window (within the PICKIT app - altough it's a little clunky if you ask me). I 've actually pimped my PICKIT2 board by soldering on a little switch which allows me to quickly switch between the PICKIT as a 'programming device' & the PICKIT 2 as a 'serial interface device' ....so no need to change the PICKIT2 edge connector now :-)

Anyway, I'm on the final straight...my query now relates to Terminal Window formatting (or rather whatever it takes to get the PICKIT 2 UART window to clear down!)

Can anyone outline (in simple terms), how I can send simple 'clear screen', line feed commands etc using the HSEROUT command?

here's a little of my code (you've not to laugh!)

ADCIN 0, DC_Level_IN ; Read the DC level on RA0 (pin 19)
HSEROUT ["ADCIN Value = ", DEC DC_Level_IN]

The problem with the above method is it's very hard on the eyes, as ithe data progresses across the screen left to right. Ideally I'd like each update to appear on a new line (or even just totally clearing the screen before the data is updated each time)

Many thanks in anticipation.

Hank.

[Archangel]

ADCIN 0, DC_Level_IN ; Read the DC level on RA0 (pin 19)
HSEROUT ["ADCIN Value = ", DEC DC_Level_IN]

The problem with the above method is it's very hard on the eyes, as ithe data progresses across the screen left to right. Ideally I'd like each update to appear on a new line (or even just totally clearing the screen before the data is updated each time)

Many thanks in anticipation.

Hank.

Try:
[code]
HSEROUT [254,1,"ADCIN Value = ", DEC DC_Level_IN]
[code]

[Archangel]

ADCIN 0, DC_Level_IN ; Read the DC level on RA0 (pin 19)
HSEROUT ["ADCIN Value = ", DEC DC_Level_IN]

The problem with the above method is it's very hard on the eyes, as ithe data progresses across the screen left to right. Ideally I'd like each update to appear on a new line (or even just totally clearing the screen before the data is updated each time)

Many thanks in anticipation.

Hank.

Try:

HSEROUT [254,1,"ADCIN Value =  ", DEC DC_Level_IN]

[Archangel]

Damn, need the edit feature back . .

[HankMcSpank]

Thanks for trying to help me out Joe, but it didn't solve my problem...



(though I'm seeing lots of little rectangles after the data onscreen now - perhaps such unexpected results is a quirk of Microchips' UART tool window?)

[HankMcSpank]

This works intermittedly...

HSEROUT [10,13," Increase Gain, ADCIN Value = ", DEC DC_Level_IN]

...about 4 times out of 10, I get a new line!

I've tried changing the baud

DEFINE HSER_BAUD 2400

...but I just get garbage when i do (yes, I'm changing the setting in the UART window too!). therefore I'm thinking this might the general flakiness of the internal oscillator &/or the quirkiness of the Microchip UART window?

[Archangel]

Thanks for trying to help me out Joe, but it didn't solve my problem...

(though I'm seeing lots of little rectangles after the data onscreen now - perhaps such unexpected results is a quirk of Microchips' UART tool window?)

I misread your post, I thought you were sending to a serial LCD.