Jump to content

dilinger

Members
  • Content Count

    71
  • Joined

  • Last visited

Community Reputation

36 Excellent

About dilinger

  • Rank
    Star Raider
  • Birthday 02/13/1966

Profile Information

  • Gender
    Male
  • Location
    Montreal

Recent Profile Visitors

4,969 profile views
  1. Thank you for the update. I had a look at the ELF format support. I use Vasm and Vlink, the makefile for your demo was easy to adapt. Unfortunately, I'm not able yet to have a ELF executable due to the reference to undefined symbols: U235SE_playback_rate U235SE_playback_period U235SE_ptr_sample_bank U235SE_playmod U235SE_pad1 U235SE_sfxplaylist_ptr However, these symbols are in the dsp.elf.obj symbol table. What tool have you used to generate the dsp.elf.obj file?
  2. The 240p test suite version source code is written in C and, depend the platforms, assets are encoded in asm. Never heard about this tool but thank you to have bring it up.
  3. I have attached a screenshot of what I see.The code is storing a value in the ROM. I have tried it with "Allow writes to cartridge ROM" option on and off, and both show the message box; with this option on, the code should be allowed to do it without message box. I will check my modifications in the emulator with the option set as on; in the meantime, you can also check your code to avoid the ROM writing. Regarding the video output, I have to put it back sooner or later.
  4. Sorry about this trouble. I'm not using the .cof format, only the ELF/DWARF one. I can check if I can write the message in the command line or the log file. In the Alpine or Debugger tab configurations, you can also turn off the rom check writing detection, it will not display the message boxes. In your case, the PC executable points outside the Jaguar address ranges, so a problem may occur in your code or in the emulator. Could you send me your testjag.cof file?
  5. Hi, I wanted to share a new version of my Virtual Jaguar modifications to include a debugger. Except the screenshot feature, the new features are programming oriented. https://github.com/djipi/Virtual-Jaguar-Rx/releases I do changes and add features for my needs/requirements so it may be not relevant to you at all. The "Allow writes to cartridge ROM" option on and off has been fixed.
  6. Beside the object list refresh, you can also keep the illegal and set his vector #4 in accordance and do whatever you want (infinite loop in your case). Vector #, Address, Exception name, Trigger condition 0, 000000, Reset SP, Not really a vector. Used to initialize the stack pointer. 1, 000004, Reset PC, Reset/startup 2, 000008, Bus error, Bus cycle couldn't complete properly. 3, 00000C, Address error, Misaligned (odd) word or longword memory access. 4, 000010, Illegal instruction, Tried executing an invalid opcode.
  7. Hi, I'm looking to create a timer, I have read there is a Programmable Interrupt Timer but I'm looking for source code example(s) to handle such interrupts using the CPU. Thank you,
  8. Hi, I have tried your new package within the ELF format and I have the same issues as the previous package. I got some warnings in u235se.inc, not a big deal but just had the wish to report them. The symbol <U235SE_sfxplaylist_ptr> is defined 2 times; the remaining warnings are redefinition symboles: U235SE_ptr_sample_bank, U235SE_playmod and a_vde. There are also various imported symbols not referenced but doesn't prevent the assembly. Unfortunately, I'm not able yet to have a ELF executable due to the reference to undefined symbols: U235SE_playback_rate U235SE_playback_period U235SE_ptr_sample_bank U235SE_playmod U235SE_pad1 U235SE_playmod U235SE_sfxplaylist_ptr
  9. Thank you for the source code. I had a look at it with the GFA Basic on Windows. I've some memory of the Basic GFA on Atari ST, hopefully it will be enough. I will keep you updated.
  10. Hi, Thank you for the information about JiFFI; well, I will have a look at the source if you will decide to release it. I just had the wish to add a feature in the tool. Unfortunately COFF format is no longer supported by recent GNU (gcc, binutils, etc.). ELF format supports also the DWARF debug format which can be handy for debugging in C and a little bit for asm. I guess we can close the thread now.
  11. I wanted to have a look at your ELF object. I have used your demo, it was easy to adapt his makefile for vasm and vlink. However I got some warnings in u235se.inc, one of them is probably easy to fix: The symbol <U235SE_sfxplaylist_ptr> is defined 2 times. Unfortunately, I'm not able yet to have a ELF executable due to the reference to undefined symbols: U235SE_playback_rate U235SE_playback_period U235SE_ptr_sample_bank U235SE_playmod U235SE_pad1 U235SE_playmod U235SE_sfxplaylist_ptr These symbols are in the dsp.elf.obj symbol table but considered as *UND*. Could you tell me with what tool you have generated the dsp.elf.obj file?
  12. Hi, I wish to know if the Jiffi tool source code is available, I would like to add the ELF format or to know if such support is planned by the tool author(s)? Thanks,
  13. I use vasm, vlink and gcc; everything with ELF format. Talking about ELF, does the Jiffi tool source code is available? I would like to add the ELF format.
  14. I'm using it as well. I have notice smaller size code than previous much older gcc versions (using the same compiling options) but there are also some weird 'nop' instruction usage here and there for no obvious reason(s). I've used the version 9 too but this is a Work in Progress.
×
×
  • Create New...