2

Author Topic: fast tiny & mega bootloader AND ATMega168  (Read 2421 times)

0 Members and 1 Guest are viewing this topic.

Offline pomprockerTopic starter

  • Supreme Robot
  • *****
  • Posts: 1,430
  • Helpful? 16
  • Sorry miss, I was giving myself an oil-job.
fast tiny & mega bootloader AND ATMega168
« on: July 30, 2008, 12:03:37 AM »
I seem to be getting nothing, but when I occasionally do get something I get this:

Bootloader VFFFFFFFF.FF
Error, wrong device informations


I've gone through Admin's bootloader tutorial a million times, I practically have it memorized.

Offline pomprockerTopic starter

  • Supreme Robot
  • *****
  • Posts: 1,430
  • Helpful? 16
  • Sorry miss, I was giving myself an oil-job.
Re: fast tiny & mega bootloader AND ATMega168
« Reply #1 on: July 30, 2008, 09:30:59 PM »
i got it working.

I just recompiled the bootloader on my own instead of using admins bootloader168.hex

Offline Admin

  • Administrator
  • Supreme Robot
  • *****
  • Posts: 11,659
  • Helpful? 169
    • Society of Robots
Re: fast tiny & mega bootloader AND ATMega168
« Reply #2 on: August 09, 2008, 08:25:13 AM »
Just in case my bootloader168.hex is corrupted, can you post it here?

Offline pomprockerTopic starter

  • Supreme Robot
  • *****
  • Posts: 1,430
  • Helpful? 16
  • Sorry miss, I was giving myself an oil-job.
Re: fast tiny & mega bootloader AND ATMega168
« Reply #3 on: August 09, 2008, 11:53:31 AM »
I don't think it is.

I did a Unix "diff" (diff - compare files line by line) on the two hex files and there was absolutely no difference.

So I don't know what the deal was. Maybe a loose nut on my keyboard.  :P

Offline dunk

  • Expert Roboticist
  • Supreme Robot
  • *****
  • Posts: 1,086
  • Helpful? 21
Re: fast tiny & mega bootloader AND ATMega168
« Reply #4 on: September 07, 2008, 01:02:18 PM »
i've just been playing with this bootloader in a windows virtual machine.
this error seems to be related to the virtual serial port FIFO buffer on the PC not passing data quickly enough for the bootloader running on the microcontroller.

if you see it occasionally just ignore and retry but if it's occurring all the time
the solution is to free up more system resources. close some unused programs.

or in my case, increase the amount of memory assigned to the virtual machine.


dunk.

 


Get Your Ad Here