Making one chip program another

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm teaching a Tiny2313 to program a Tiny24. The literature is iffy, but I think I have enough going to at least get back the 0x53 echo from my target during word 3. I'm not.

Anyone got advice on driving serial programming algorithms ?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You can check out ButtLoad (written by abcminiuser). He did serial programming in that.

Regards,
Steve A.

The Board helps those that help themselves.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Steve. Too much to read. Got over the hump, though. MISO'd when I should have MOSI'd

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Are you using ISP?

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If you understand ASM then have a look at the AVR910 application note from Atmel, the code runs on a Tiny2313 (originally a 1200). You will need to modify the code to suit the T24.

This is the last version I played with. https://www.avrfreaks.net/index.p...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Affirmative to the isp. AVR 910 is a better read. I've got code moving and the address is off, but I'm close. My end game is having 8515's put code into Mega 103's for which we no longer have (if we ever had) source code. P.S. Don't tell my boss I'm having fun hacking this. :wink:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I'm teaching a Tiny2313 to program a Tiny24. The literature is iffy, ...

Well, it may be--but it really is not.

All of the "AVR910"-type programmers do exactly that--have one AVR program another. That code has been around for ages, and all of the earlier incarnations were built for a '2313. Now, they would communicate to a host to get a buffer/command at a time, but that part needs to be handled anyway--where are you going to store 2k of firmware on a 2k chip anyway?

As far as the actual algorithm for a Tiny24 that should not be anything special compared to similar chips of that generation.

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Off-Earth wrote:
Affirmative to the isp. AVR 910 is a better read. I've got code moving and the address is off, but I'm close. My end game is having 8515's put code into Mega 103's for which we no longer have (if we ever had) source code. P.S. Don't tell my boss I'm having fun hacking this. :wink:

I'm curious, why would you need source code? all one needs is the resultant hex file. If this is simply about programming mega103's you can do that with the AVRISP... or is there some specific reason why you need to do it with another AVR?

Writing code is like having sex.... make one little mistake, and you're supporting it for life.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have a similar need (I want to build a standalone programmer to quickly program M1281-based units). I am assuming Off-Earth can't share his code, so I'll still have to roll my own.

Jim

Jim Brain

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I am assuming Off-Earth can't share his code, so I'll still have to roll my own.

Or look at Dean's ?

(search "buttload")

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Concerning source vs. hex. With source I would re-spin the board with a newer processor. The company won't splurge for the 501, so I'm making one µ do the other. The code now works for a 2313, 8515 (attached) and the Mega16.

The attached code for 8515:
I write as I have written for 30 years. Pseudo code is the annotation and I put the instructions in that performs the step. Not conventional, but fast.

This particular code has the extra added feature of being ugly because I spent a whole 8 hours on it.

Attachment(s):