04 February 2006, 11:59 | #1 |
Registered User
Join Date: Nov 2005
Location: United Kingdom
Age: 40
Posts: 100
|
Barfly misidentifies 68020 under emulation
I've noted while developing under WinUAE that Barfly Assembler refuses to run with either 68020 or 68020+FPU processor modes, stating that you need a 68020 or higher - which seems a little odd :-)
Now, as far as I know Barfly works fine on a real 68020 so I thought I'd raise the issue here as a possible bug in the emulation. Cheers, M;. |
04 February 2006, 12:08 | #2 |
Peter
Join Date: Oct 2004
Location: Sowerby Bridge,UK
Age: 57
Posts: 102
|
Maybe its looking for the more commom 680EC020 processor found in the A1200.
|
04 February 2006, 13:15 | #3 |
Registered User
Join Date: Nov 2005
Location: United Kingdom
Age: 40
Posts: 100
|
Well, if that's the case it doesn't recognise 68EC020 mode in WinUAE either :-)
|
04 February 2006, 14:21 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,505
|
version? both barfly and winuae
|
04 February 2006, 16:42 | #5 |
Registered User
Join Date: Nov 2005
Location: United Kingdom
Age: 40
Posts: 100
|
Barfly is version 2.9 available on Aminet - the last version AFAIK and also distributed with a free registered key
WinUAE is the latest build 1.1.1 as available on winuae.net M;. |
04 February 2006, 16:50 | #6 |
Registered User
Join Date: Nov 2005
Location: United Kingdom
Age: 40
Posts: 100
|
Also, if it helps, Barfly does the following test in its code to determine a 68020+ processor:
;execbase in a6 btst #2,$129(a6) beq _notsupported I actually looked into this myself - bit #2 is actually the 68030 flag of the AttnFlags field - so it is infact Barfly that is at fault (if indeed it was ever meant to support 68020s in the first place) - I expect I was using an older version at the time of my 020 A1200 so hence why it probably worked :-) Never mind eh? M;. Last edited by DJ Mike; 04 February 2006 at 17:09. |
04 February 2006, 21:07 | #7 |
Moderator
Join Date: Nov 2001
Location: Germany
Posts: 866
|
have basm already successful used under uae!
for the debugger you need to disable jit. |
04 February 2006, 22:21 | #8 |
Registered User
Join Date: Nov 2005
Location: United Kingdom
Age: 40
Posts: 100
|
Actually to get BAsm to work you can just select 68040 for the CPU - I raised the issue as a possible bug in emulation just to make the authors aware of it.
|
11 February 2006, 12:39 | #9 |
2 contact me: email only!
Join Date: May 2001
Location: Auckland / New Zealand
Posts: 3,182
|
If you are using Barfly 2.9 (171728 bytes) on a 68020, you can change offset $4aa from $0002 to $0001 and it will then work as DJ Mike noticed!
|
24 May 2006, 23:37 | #10 |
Zone Friend
Join Date: May 2006
Location: France
Posts: 1,801
|
Hi
Set the cpu to 68040 under UAE and Barfly will work. kamelito |
02 March 2007, 06:08 | #11 | |
move.l #$c0ff33,throat
Join Date: Dec 2005
Location: Berlin/Joymoney
Posts: 6,863
|
Quote:
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
UAE4All 68020-emulation fix | john4p | support.OtherUAE | 16 | 17 January 2014 08:18 |
68020 33 MHz | Leandro Jardim | support.WinUAE | 2 | 02 January 2012 19:21 |
Questions about 68020 CE | Maren | support.WinUAE | 11 | 09 December 2009 21:01 |
RANDOM BARFLY bug compiling EOB1ECS-AGA (need help) | CFou! | Coders. General | 10 | 02 September 2008 01:00 |
Looking Barfly asm | Oneillsite | Coders. General | 4 | 25 September 2006 20:27 |
|
|