WinAVR Release Candidate

Go To Last Post
67 posts / 0 new

Pages

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

I havn't looked in WinAVR 20070525 "final" yet (was in holidays in Spain ;-) I'll inform you soon whether a patch is required at all.

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

I have final WinAVR 20070525 and Win 98 - unfortunately patch IS required.

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

drzonca wrote:
I have final WinAVR 20070525 and Win 98 - unfortunately patch IS required.

Same result here with Windows98SE.

The binary patched avr-gcc.exe is attached. In the archive is also a small description how to find the patch position via disassembling.

Maybe other tools require the same patch - please write when you get the _spawnv error with other tools.

Stefan

Attachment(s): 

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

What is the issue in the source code that the binary patch fixes? I'd rather get this fixed in the source code...

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

See https://www.avrfreaks.net/index.p...

The issue is a incompatibility of the format of parameter 'executable' with the _spawnv() function in Windows98 MSVCRT.DLL (MS C Runtime Library).

'executable' contains slashes as seperators and _spawnv() of MSVCRT.DLL (or to be more precise some of _spawnv's subfunctions such as access() and CreateProcess()) chokes on this.

Maybe this is fixed in later MSVCRT.DLLs on other Windows systems. I have MSVCRT.DLL version 6.10.9844.0 from Visual C++ 6. More investigations would require debugging different MSVCRT.DLL versions on different Windows systems.

I can understand when a source change in GCC's pex-win32.c is not considered. It is not a task of the GCC-team to fix older libraries of MS.

I poke 2 bytes in avr-gcc.exe and i am happy when the program works with the "broken" MSVCRT.DLL. The effect is, that the parameter 'executable' is replaced by the parameter 'newargv[0]'. This is a backslashified version of 'executable'.

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

StefB wrote:
The binary patched avr-gcc.exe is attached. In the archive is also a small description how to find the patch position via disassembling.

Thank you very much! Patched version works fine, tested.

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

StefB wrote:
The binary patched avr-gcc.exe is attached. In the archive is also a small description how to find the patch position via disassembling.

Strange... but did not work for me :(

AVRStudio version:

AVR Studio        4.12.498  Service Pack 4
GUI Version       4, 12, 0, 491
AVR Simulator     1, 0, 1, 8
AT90PWM3          153

Operating System
Major             4
Minor             10
PlatformID        1
Build             67766446

Windows 98SE 4.10.2222
msvcrt.dll 6.10.9844.0
WinAVR.20070525

I replaced the avr-gcc.exe and also avr-gcc-4.1.2.exe still no change.

Build started 22.6.2007 at 13:30:45
avr-gcc.exe  -mmcu=at90pwm3 -Wall -gdwarf-2 -O0 -MD -MP -MT pwm3.o -MF dep/pwm3.o.d  -c  ../pwm3.c
avr-gcc.exe: _spawnv: No such file or directory
make: *** [pwm3.o] Error 1

What else to check?

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

WinAVR20070525 output is NOT compatible with AVR Studio 4.12.491. You must upgrade to 4.13.528 which the understands the 32 bit ELF debugging format now generated by 20070525

Cliff

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

Wow! That was really fast reply. OK, upgraded to 4.13.528. Still the same. I will try on second machine with Win 2k.

UPDATE:
On fresh Win 2k the installer of AStudio.4.13 had problems, manual copy of some dll files (Visual Studio 8 runtime libraries) was necessary, but finally there is no error as in Win 98SE...
Any help on what can I else check to run it on Win 98SE?

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

AVR Studio 4.13 on Windows 98SE is difficult. I have some projects that work, others not (exception when project is opened). I avoid AVR Studio om Windows 98SE.

Sure there were no problems with overwriting original avr-gcc.exe? Try to compare original avr-gcc.exe and patches avr-gcc.exe with a hexeditor. There should be differences in three bytes. I have no other idea how to help you, sorry.

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

Finally I gave up on trying to run it on 98SE. Tried both avr-gcc patches and replacing some dll files in windows/system to different versions. Even on clean 98SE with "unofficial" service pack (hxxp://sp.up.pl/) - still the same. For sure it has nothing to do with install directories - checked several different locations. Those constant exceptions while trying to open an existing project got really annoying. Strange that creating new project works fine.

However, I got sometimes the same exception on 2k if I open projects from startup wizard, so I disabled it in options and open projects from menu. Works fine. Still bothers me why the installer on 2k reports errors with registering some dll files and where to get required mfc80 runtime libraries (luckily I had them on my 98SE, but what program installed those I have no idea). Till now it seems that on 2k everything works despite installer errors.

Thanks for help anyway :wink:

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

Not settled the program all full day until now.
Thanks so much! :o

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

Just FYI I had this issue on XP Professional SP1 machine, used the patch from this post and fixed it - thanks a lot!

I am still learning...

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

Thank you, Eric!

I just tried WinAVR-20071221 with Windows98SE. It worked right out of the box. No _spawnv errors like in previous versions.

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

Thanks for the feedback! I'm glad it worked for you!

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

madwizard wrote:
Good news on the Vista 64 front, I have a working msys DLL that shows no problems on Vista 64-bits! I just got an e-mail confirming that without this DLL WinAVR RC2 does not work on Vista 64 (same error as before), but after changing the DLL it was fixed and behavior was the same as on Vista 32.

It is still the same patch as described on Nabble but I made two modifications. Unfortunately I do not know yet whether both modifications are necessary but that can be easily tested with some more test versions.

Anything ever come of this? The link in the other thread is dead, and I don't see anything on your Vista page.

Thanks.

Edit: For anyone else with this problem, I found the link (I was looking at the wrong post) http://www.madwizard.org/extern/...
Install 20070525 and copy this dll into utils\bin, it seems to be working for me.

Pages