Page 24 of 43 FirstFirst ... 1420212223242526272834 ... LastLast
Results 231 to 240 of 427

Thread: M68K for DC

                  
   
  1. #231
    DCEmu Coder
    Join Date
    Apr 2004
    Location
    FRANCE
    Posts
    80
    Rep Power
    0

    Default Re: M68K for DC

    Ian>
    I uploaded the special NeoCD version of C68K (it include your HLE stuff) :
    http://gens.consolemul.com/download/C68K_bin_neocd.zip

    It's directly the binaries files :
    - c68k.o
    - c68kexec.o

    both has been compiled with -0s switch

    Don't forget it's only for NeoCD, it need Neoxxx externals... you can't use it for Genesis Plus etc ...

    have fun

  2. #232
    DCEmu Regular
    Join Date
    Apr 2004
    Location
    Posts
    351
    Rep Power
    79

    Default Re: M68K for DC



    Im sorry im lost or have lost it take your pick. i have to say Â*i really have got no clue about adding this now. I thought i did but i get these and i dont know what else to add. I was told your core is now api complent that means to me i dont change the emulator at all and can drop the core in. But i just dont get what you want me to do to make this compile. For the old core it's easy 2 make files it makes the m68k.a i link it in.

    Help sorry for being a pain Â*


    thanks for all your work stef.

    :-[

    Can you tell me Â*what files but these do i need to add.??????
    Code:
    c68/c68k.o c68/c68kexec.o z80/z80.o Â*z80/z80intrf.o Â*neocdc.o vmu/vmu.o 
    
    memory/memory.o cdrom/cdrom.o cdrom/dc.o Â*cdaudio/cdaudio.o Â*sound/sound.o sound/streams.o 
    
    sound/2610intf.o sound/ay8910.o Â* sound/fm.o Â*sound/timer.o sound/ymdeltat.o Â*video/videopvr.o 
    
    video/draw_fix.o Â*swab.o input/input.o pd4990adc.o
    Â*

    thats all i have what more do i need to add so i dont get the errors



    Code:
    neocdc.o: In function `neogeo_init':
    neocdc.o(.text+0x8a8): undefined reference to `m68k_pulse_reset'
    neocdc.o: In function `neogeo_hreset':
    neocdc.o(.text+0xac8): undefined reference to `m68k_set_reg'
    neocdc.o(.text+0xad0): undefined reference to `m68k_pulse_reset'
    neocdc.o: In function `neogeo_reset':
    neocdc.o(.text+0xd1c): undefined reference to `m68k_pulse_reset'
    neocdc.o(.text+0xd20): undefined reference to `m68k_set_reg'
    neocdc.o: In function `MC68000_Cause_Interrupt':
    neocdc.o(.text+0x1088): undefined reference to `m68k_set_irq'
    neocdc.o: In function `neogeo_run':
    neocdc.o(.text+0x1264): undefined reference to `m68k_execute'
    neocdc.o(.text+0x126c): undefined reference to `m68k_set_irq'
    neocdc.o: In function `neogeo_prio_switch':
    neocdc.o(.text+0x1424): undefined reference to `m68k_get_reg'
    neocdc.o: In function `neogeo_cdda_control':
    neocdc.o(.text+0x152c): undefined reference to `m68k_get_reg'
    cdrom/cdrom.o: In function `cdrom_load_files':
    cdrom/cdrom.o(.text+0x1374): undefined reference to `m68k_get_reg'
    What should i change these functions to is there news names do i need the m68k old core and this one.

    totaly lost

    Ian

  3. #233
    DCEmu Coder
    Join Date
    Apr 2004
    Location
    FRANCE
    Posts
    80
    Rep Power
    0

    Default Re: M68K for DC

    No problems
    Well, when i said C68K is musashi complient, actually there are still some differences...
    and the least, the fonctions names are different !
    where musashi is : m68k_xxx
    C68K is : C68K_xxx

    and anyway some functions has complete different name, but they do the same work, and take sames parameters
    Well, actually i think you still should keep musashi in your NeoCD sources, C68K should stay an alternative, just for experiment purposes
    So you should take the CPU interface i made with Genesis Plus : cpu68k.c and cpu68k.h file
    also don't forget to include the C68K header file (c68k.h) in your project, you can take all that from my last sources of Genesis Plus DC :
    http://gens.consolemul.com/download/GenPlus_DC.zip


    Well, as you added that to the project, you'll have to replace all m68k_xxx functions by M68K_xxx functions (which are from the CPU interface).
    depending current CPU core definition in cpu68.h file, the CPU interfacer will use musashi or C68K methods

    You will have to modify the M68K_Init function as well to add the good prefetch area in C68K...
    Hmmm... actually i'm thinking they are many changes to do :-/ also the memory functions, interrupt callback ...
    Well, just try to do the first points, then post as soon you're lock ed somewhere and i'll help you... you can also get me in touch with ICQ or MSN if you want






  4. #234
    Dream Coder
    Join Date
    Apr 2004
    Location
    Miami, FL
    Age
    38
    Posts
    4,675
    Rep Power
    50

    Default Re: M68K for DC

    I was able to get it mostly in, but i was using the first c68k sources you posted, not the ones from Genplus, maybe that makes a difference. I think it would have worked except the main neocd file had to be rewritten in a lot of parts.
    If anyone is looking to buy, sell, trade games and support a developer directly at the same time, consider joining Goozex. Enjoy!

  5. #235
    DCEmu Coder
    Join Date
    Apr 2004
    Location
    FRANCE
    Posts
    80
    Rep Power
    0

    Default Re: M68K for DC

    [quote author=quzar link=board=dcemu;num=1083323639;start=225#233 date=06/21/04 at 08:19:31]I was able to get it mostly in, but i was using the first c68k sources you posted, not the ones from Genplus, maybe that makes a difference. I think it would have worked except the main neocd file had to be rewritten in a lot of parts.[/quote]

    The first C68K files are even less friendly with musashi ...
    Futhermore, you don't have the HLE stuff included :-/
    To make NeoCD working correctly you should use the C68K_bin_neocd.zip obj files
    Of course, you also need to take c68k.h file and cpu niterface from GenPlus_DC.zip archive ...
    then some work is needed to succefully include it in NeoCD ...Where is the last NeoCD sources archive ? if i've some free time, i'll try to look into that...

  6. #236

    Default Re: M68K for DC

    That's the latest public archive I believe:

    http://imrtechnology.ngemu.com/emulators.htm

    http://imrtechnology.ngemu.com/downloads/v8.1src.rar

    It's really nice to see you people working so close together!


    Chris

  7. #237
    Dream Coder
    Join Date
    Apr 2004
    Location
    Miami, FL
    Age
    38
    Posts
    4,675
    Rep Power
    50

    Default Re: M68K for DC

    [quote author=Stef link=board=dcemu;num=1083323639;start=225#234 date=06/21/04 at 09:10:35]

    The first C68K files are even less friendly with musashi ...
    Futhermore, you don't have the HLE stuff included :-/
    To make NeoCD working correctly you should use the C68K_bin_neocd.zip obj files
    Of course, you also need to take c68k.h file and cpu niterface from GenPlus_DC.zip archive ...
    then some work is needed to succefully include it in NeoCD ...Where is the last NeoCD sources archive ? if i've some free time, i'll try to look into that...[/quote]

    I did have the NeoCD object files I was close but just tired (it was like 6am). Also i was using the outdated first release c68k headers. Ill try it now with the files from GenPlus and the neocd object files.
    If anyone is looking to buy, sell, trade games and support a developer directly at the same time, consider joining Goozex. Enjoy!

  8. #238
    Dream Coder
    Join Date
    Apr 2004
    Location
    Miami, FL
    Age
    38
    Posts
    4,675
    Rep Power
    50

    Default Re: M68K for DC

    Sorry for the double post, but also, how can i compile the GenPlus with c68k? The makefile included says nothing about c68k =(
    If anyone is looking to buy, sell, trade games and support a developer directly at the same time, consider joining Goozex. Enjoy!

  9. #239
    DCEmu Regular
    Join Date
    Apr 2004
    Location
    Posts
    351
    Rep Power
    79

    Default Re: M68K for DC

    Hmm ive looking at it cant sleep im now having nitemares about adding this.

    Interface headers
    // 68K CPU interface

    #include "types.h"
    #include "cpu68k.h"
    #include "c68k.h"
    #include "m68k.h"
    #include "m68kcpu.h"
    #include "mem68k.h"
    //#include "genesis.h" Â*i dont think i should include this.


    problem do i have to compile and edit the files that are the same names as these headers but c files there heavly baised to genesis plus if i compile them c files it conflicts with functions and i endup including most of genesis plus in neogeo cd. Â*

    Just want to know do i have to compile any more files then what you have told me???.

    c68/c68k.o c68/c68kexec.o c68/cpu68k.o Â*cpu core correct?

    headers to included in the cpu interface file.

    change the define Â*in Â*cpu68k.h

    #define CPU68K_USE_MUSASHI
    //#define CPU68K_USE_C68K

    errors now

    Code:
    c68/cpu68k.c:32: warning: static declaration for `M68K_Init' follows non-static
    c68/cpu68k.c: In function `M68K_Init':
    c68/cpu68k.c:37: `m68k_irq_ack_callback' undeclared (first use in this function)
    
    c68/cpu68k.c:37: (Each undeclared identifier is reported only once
    c68/cpu68k.c:37: for each function it appears in.)
    c68/cpu68k.c: At top level:
    c68/cpu68k.c:58: warning: static declaration for `M68K_Reset' follows non-static
    
    c68/cpu68k.c:69: warning: static declaration for `M68K_Exec' follows non-static
    c68/cpu68k.c:80: warning: static declaration for `M68K_SetIRQ' follows non-stati
    c
    c68/cpu68k.c:91: warning: static declaration for `M68K_GetOdo' follows non-stati
    c
    c68/cpu68k.c:102: warning: static declaration for `M68K_EndExec' follows non-sta
    tic
    c68/cpu68k.c:114: warning: static declaration for `M68K_SetFetch' follows non-st
    atic
    c68/cpu68k.c:126: warning: static declaration for `M68K_GetDReg' follows non-sta
    tic
    c68/cpu68k.c:137: warning: static declaration for `M68K_GetAReg' follows non-sta
    tic
    c68/cpu68k.c:148: warning: static declaration for `M68K_GetSP' follows non-stati
    c
    c68/cpu68k.c:153: warning: static declaration for `M68K_GetPC' follows non-stati
    c
    c68/cpu68k.c:164: warning: static declaration for `M68K_GetSR' follows non-stati
    c
    c68/cpu68k.c:175: warning: static declaration for `M68K_SetDReg' follows non-sta
    tic
    c68/cpu68k.c:186: warning: static declaration for `M68K_SetAReg' follows non-sta
    tic
    c68/cpu68k.c:197: warning: static declaration for `M68K_SetSP' follows non-stati
    c
    c68/cpu68k.c:213: warning: static declaration for `M68K_SetSR' follows non-stati
    c


    What step im i missing i just want to get this to compile for a change so i can work on Â*rewriting the functions.

    EDIT ok found one error

    int m68k_irq_ack_callback(int int_level);

    s32 FASTCALL m68k_irq_ack_callbackf(s32 int_level);

    in genesis.h i need to move that dont know what else i need from the header yet.

    Now i get this i went past the first error

    Code:
    rnel/arch/dreamcast/include -c z80/z80intrf.c -o z80/z80intrf.o
    In file included from neocd.h:19,
     Â* Â* Â* Â* Â* Â* Â* Â* from z80/z80intrf.c:6:
    c68/c68k.h:82: parse error before "FASTCALL"
    c68/c68k.h:82: parse error before "adr"
    c68/c68k.h:82: warning: data definition has no type or storage class
    c68/c68k.h:83: parse error before "C68K_WRITE"
    c68/c68k.h:83: parse error before "adr"
    c68/c68k.h:83: warning: data definition has no type or storage class
    c68/c68k.h:85: parse error before "FASTCALL"
    c68/c68k.h:85: parse error before "level"
    c68/c68k.h:85: warning: data definition has no type or storage class
    c68/c68k.h:86: parse error before "C68K_RESET_CALLBACK"
    c68/c68k.h:86: warning: data definition has no type or storage class

    ??

    #define FASTCALL Â*?

    #define FASTCALL
    #define C68K_READ
    #define C68k_Get_MSP
    #define C68K_INT_CALLBACK

    so make defines for every error? removes them but hmm..

    Ok i got it to this

    Code:
    c68/cpu68k.o: In function `M68K_SetPC':
    c68/cpu68k.o(.text+0x6c): undefined reference to `m68k_set_reg'
    c68/cpu68k.o: In function `M68K_Disassemble':
    c68/cpu68k.o(.text+0xa4): undefined reference to `m68k_disassemble'
    neocdc.o: In function `neogeo_hreset':
    neocdc.o(.text+0xac8): undefined reference to `m68k_set_reg'
    neocdc.o(.text+0xad0): undefined reference to `m68k_pulse_reset'
    neocdc.o: In function `neogeo_reset':
    neocdc.o(.text+0xd1c): undefined reference to `m68k_pulse_reset'
    neocdc.o(.text+0xd20): undefined reference to `m68k_set_reg'
    neocdc.o: In function `MC68000_Cause_Interrupt':
    neocdc.o(.text+0x1088): undefined reference to `m68k_set_irq'
    neocdc.o: In function `neogeo_run':
    neocdc.o(.text+0x120c): undefined reference to `m68k_execute'
    neocdc.o(.text+0x121c): undefined reference to `m68k_set_irq'
    neocdc.o: In function `neogeo_prio_switch':
    neocdc.o(.text+0x13c4): undefined reference to `m68k_get_reg'
    neocdc.o: In function `neogeo_cdda_control':
    neocdc.o(.text+0x14cc): undefined reference to `m68k_get_reg'
    cdrom/cdrom.o: In function `cdrom_load_files':
    cdrom/cdrom.o(.text+0x1374): undefined reference to `m68k_get_reg'

  10. #240
    Dream Coder
    Join Date
    Apr 2004
    Location
    Miami, FL
    Age
    38
    Posts
    4,675
    Rep Power
    50

    Default Re: M68K for DC

    I know how to fix those. ill tell you on msn
    If anyone is looking to buy, sell, trade games and support a developer directly at the same time, consider joining Goozex. Enjoy!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •