BLIPS win7 64 bit replacement / AVRDude help

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

Hi all

 

I recently updated my laptop to a Win 7 Pro 64 bit machine (wasn't going Win 8) from my old Win 7 Pro 32 bit machine. I've just discovered that BLIPS doesn't seem to work. It has the MSWINSCKS.OCX error. For some reason I don't seem to be able to register that manually. But I figured I've been using BLIPS for about 10 years now. Surely there must be something newer? Google seems to suggest there isn't. Can anyone recommend anything?

 

I've tried AVRdude (why are we still in a command line world?) with no luck. My line is:

 

avrdude -p m64 -b 9600 -P com5 -c avr100 -e -U flash:w:"filename.hex":a

 

and the response is:

 

Connecting to programmer: .
Found programmer: Id = "Mega64 "; type = S
    Software Version = 1.2; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=256 bytes.

Programmer supports the following devices:
    Device code: 0x44

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.04s

avrdude: Device signature = 0x1e9602
avrdude: error: programmer did not respond to command: set addr

 

I can tell from the LCD on my device that it enters bootloader mode (I have to hold down a button too), then within about a second it restarts, and then of course avrdude can't program. My bootloader normally times out within about 5 seconds, not 1, so I guess that somewhere avrdude is forcing a reset?

 

I know the bootloader works. I've been using it with BLIPS for about 10 years now. I have 1000s of devices sold around the world that I have to support so it's not really feasible to change my bootload code. It still works with an old machine running BLIPS. Does anyone have any ideas on what I should be looking for to get it working on Win 7 Pro 64 bit?

 

Cheers - Matt

 

 

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

While you could add more and more -v's to the avrdude command there to see the specifics the very fact that it responds with figures like the 256 byte page size suggests the PC and the AVR are talking. So I doubt this is a high-level PC thing causing problems.

why are we still in a command line world?

Some of us luddites would prefer if we'd never left it! I just typed:

$ find . -name \*.cpp -exec grep -H arm_neon {} ";"

on something I'm working on - I haven't a clue how you'd do that with some GUI hiding the power of the command line?

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

I've never seen the programmer avr100.  Is that legitimate?

 

Every bootloader ought to respond to the set address command.

 

By the way, one potential problem with the usual bootloaders is the address given in the set address command is 16 bits (two bytes).  That can be used to program memory up to 128 k, because this address is considered a word address.  I saw in the xboot Xmega bootloader code they have a new "set extended address" ('H') command that sets a 24 bit (three bytes) address.  I don't know what PC bootloader programs use it though.  In any event I doubt that has anything to do with your problem.

 

An AVR bootloader should respond to every command (except sync).  It the command is unknown it should respond with a question mark ('?').

 

When avrdude finishes it will send the bootloader an exit command which causes the bootloader to give control to the application.  At least it does that if the programming is successful.  I'm not sure if it sends the exit command if the programming fails.

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

Sorry typo there, I am using AVR109.

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

I'm not familiar with the avr109.  I may have used it on the Butterfly a long time ago.

 

Everything is working fine until avrdude sends the set address command ('A').  At least that is the command used by the bootloaders I'm familiar with.  If you have a debugger, see what happens when it gets that command.

Last Edited: Thu. Nov 27, 2014 - 11:46 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I discovered if I run a Virtual Windows PC running XP that I can get blips to load ok. Then I can get it to talk to my application hardware which enters bootload mode ok. But sadly Blips seems to hang after reading the device ID. Off for more research..

 

Matt

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

is there no way to run that app in 32 bit compatibility mode?

 

I have played with it a long time ago on a win7 64bit home machine and IIRC things worked correct on that OS, so might have run in compatibility mode.

 

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

I tried that. BLIPS won't run as it needs mswinsck.ocx and a few other older ocx files. I tried installing them but had no luck with that. I've emailed Steve who wrote BLIPS originally to see if he has any ideas, or even whether he's willing to share the source code with me and I will update it to run on later machines. Then we can all benefit from it.