Building the SSC32

Hi!

I have recently built the ssc32. I only changed the st202 to hin232(max232 compatible).And I want to program the avr with the firmware.
I managed to program the bootloader with the corect fusebit settings…or I think so.Can I test that?
Now I want to program the firmware.But when I try it the lynxterm sends an error message.
I don’t know what I’m doing wrong.I have set the jumpers to 115.k baudrate.I connected the txd and rxd lines.I’m using a 14.7456 Mhz crystal.When should the led light up?After the firmware upgrade?
Can anybody help?I’m desperate.

Thanks

Cluoiset

Hi Cluoiset,

I’ve compiled the SSC32 code and programmed the AVR chip on a SDK500 development board. I just programmed the whole code. I don’t seem remember a boot loader.

Would you be able or want to program the entire part with the current code? What programmer do you have?

Try reading the AVR both before and after you attempt to do the boot. This might tell you where and if anything is loading.

The board doesn’t talk back much. Try issuing a “version” command (after a download).

Is the boot loader supposed to talk back or ack the download somehow?

Alan KM6VV

I managed to program the bootloader. I wanted to use this because I never used it.But I think your version would work fine.I just didn’t want to mess with the compilation.But now it works.
I used the Ponyprog programmer. I found a txt next to the bootloader hex. In it were the fuse configurations.
Now it works fine.BUt It can’t controll more than one servo at once.And I don’t know why?

Cluoiset

Hi Cluoiset,

I assume you have the correct crystal? All I can think of is that it sounds like it might be running slow? But that’s unlikely. And the fact that you’ve successfully sent a servo command says that the clock is right.

You might post the command(s) you’re sending, that might give us a clue.

Alan KM6VV

Hi!

I’m using a 14.756 Mhz crystal if my memory serves well. And it works with one servo fine.
I tried this command:
#1p1200#p2000#p1500

Cluoiset

I don’t see a servo number between the “#” and the “p” in the second and third servo move commands above. You have to have a servo number for each move or nothing is going to happen, like

#1p1200#2p2000#3p1500

would move servo #1 to 1200 uS, servo #2 to 2000 uS, and servo #3 to 1500 uS positions. I also like to have some spaces in my commands to make them more readable like

#1 p1200 #2 P2000 #3 P1500

8-Dale

Wow!

Beat me to it!

Alan KM6VV