Hi!

I am playing around with source code - trying to change messages.

I got latest WinAVR (20080610) and UsbTinyISP programmer.

Code compilation went fine, no errors.

I have configured build instructions to use UsbTintISP for microchip programming.

I got following error while programming mrb.hex:

avrdude: reading input file "mrb.hex"
avrdude: input file mrb.hex auto detected as Intel Hex
avrdude: ERROR: address 0x0810 out of range at line 129 of mrb.hex
avrdude: write to file 'mrb.hex' failed

Starting this point I have no idea what goes wrong.

I would quite appreciate if someone can comment on subject.

Thanks!

Have you tried compiling and uploading the original firmware? Also, are you (1) using an ATtiny2313, (2) using our makefile?

Hi Windell!

Yes, I have tried to compile original firmware also - I got same error while uploading flash to microcontroller.

I use ATTiny2313-20PU (0746) from Futurlec.

I use your Makefile with adjustment for UsbTinyISP programmer - $(PROGRAMMER) = usbtiny.

Thanks for your attention!

That should be okay; that's the programmer that I use... and I don't recall getting that message before.

Is your target board new? I *think* that this sort of error can possibly be caused by a wiring error-- I might be able to try and reproduce this sometime soon, but please go over your connections and make sure that they are all correct and solid.

Hi! I have re-checked my wiring, it was fine - actually I made small PCB for this reader http://img529.imageshack.us/img529/3329/dsc00959op2.jpg and all joints were well soldered. I was using WinAVR 20080610, switching back to WinAVR 20070122 solved the problem. So it looks like latest WinAVR generates bigger code. It's somewhat strange that I see no any error messages from latest WinAVR about wrong code size, usually it advices that code is big for specific device. I assume that my issue is solved - just do not use latest WinAVR 20080610 and all be fine. I just curious - which version of WinAVR do you use? Thanks a lot for your attention and wonderful kit!

I don't actually use WinAVR-- no windows computers here.

Oleg - (or anyone else!) -

I get a similar error to what Oleg reports, using the December release of WinAVR. My error reports address x080e.

Unfortunately, I'm unable to locate the download for WinAVR 20070122. I'd appreciate any pointers to that older download.

Thanks!

I now have a non-functioning Amtel...


Kevin

Are you trying to program the micro-readerboard firmware onto a '2313?

Yup: on of the kits. Modified the strings a bit as a test. "make" works - compiles with no errors. "make install" is where the fun comes. The error is after the eeprom is written, and looks like this:

avrdude: verifying ...
avrdude: 2 bytes of eeprom verified
avrdude: reading input file "mrb.hex"
avrdude: input file mrb.hex auto detected as Intel Hex
avrdude: ERROR: address 0x080e out of range at line 129 of mrb.hex
avrdude: write to file 'mrb.hex' failed

avrdude: safemode: lfuse reads as 62
avrdude: safemode: hfuse reads as DF
avrdude: safemode: efuse reads as FF
avrdude: safemode: Fuses OK

avrdude done. Thank you.

make: *** [install] Error 1

===================

I've posted this to SourceForge, but have no idea when someone may see and reply.


Kevin

Try changing the firmware to store fewer total strings; that should fix it.

Hmmmm...

Chopped string set two in half. Installs now without errors - but all that lights up is the decimal point, which never lit before! My other (unmodified) chip works just fine on the breadboard.

Gonna have to figure out how to determine memory sizes - *and* get this chip working again.


Kevin

Okay, I just revised the firmware so that it works when compiled with the latest version of the AVR toolchain. Download the new version here, now at version 2.1.

Windell - thanks! I'll be reloading the current toolchain and giving it a try.

Question: how can I readily determine if the processor is fried? As noted, it only lights up the decimal point now - no blinking or anything else... and if it's fried, what's a good source for more?

Thanks!


Kevin

If you can still program the chip it's not fried.

Ouch. Any suggestions for the cause of the noted behavior? After chopping the string set down, changing string set sizes, etc. I was able to "make install" last night. No errors... Haven't reloaded the current toolchain and mrb 2.1 yet...


Kevin