Jump to content

sanny

Members
  • Posts

    713
  • Joined

  • Last visited

Everything posted by sanny

  1. Most warnings can be ignored, but not the ones like "...overflows memory area...". There is not enough space in this area, you need to shuffle around and put something into other segments.
  2. I'd guess the example from the docs is outdated. ? Can you post that exactly did you try and the errors you got?
  3. Hmm. What is "near direct"? "Completely direct" would be "*pointer=value". "Near direct" could be something like "em_copy(void *dest, void *src, int len)". You didn't answer my question.
  4. Not really. How is it better than the existing cc65 driver? Honestly, I don't know. Can somebody chime in?
  5. Could you explain your driver? Examples how to use it?
  6. Joseph, please read the link in @Wrathchild's post from top to bottom. In chapter 4.1 there is one linker config file called "atari-cart.cfg", which is exactly what you want (create a cartridge image). In general, considering your other posts, it appears to me that you are pursuing solutions for problems which don't exist (at least for the rest of us). And you seem to be immune against good advice. I guess the best way forward would be to find a small, simple problem where you could implement a solution. regards, chris
  7. @zbyti, in your table in post #258, isn't MADS an assembler? If yes, is there a reason you write "MADS" instead of "Assembler"?
  8. And what exactly does your question have to do with "Atari 5200 / 8-bit Programming"?
  9. While we're at it: the "PBI 5 volts patch", can somebody show it to me again? I did it in on 800XL some years ago, but want to do it on another one.
  10. Joseph, aka Harry, are you really real? Or an artificial intelligence which emerged from the all-embracing internet? Seeded by aliens.
  11. You'e wrong, It _does_. That's in fact the difference between the "atari" and "atarixl" targets. For assembler programs the include file "atari.inc" defines a CIOV label which points to code to enable the ROM, call real CIOV, disable the ROM again. Since currently there is no such provision for C you'll need to write a small assembler stub which can be called by C and calls the CIOV label.
  12. Hmm. So you have code to explicitly load these areas. You can do the same on Atari, where is the problem? (Atari could do better by loading it automatically from DOS, but you seem to have problems implementing that...)
  13. As I said before, the simplest way to use this memory area in cc65 is by calling _heapadd() [https://cc65.github.io/doc/funcref.html#ss3.5] so it becomes malloc()-able. To automatically load something there from the EXE file you need to add a load chunk.
  14. This all is just plain stupid... OP, until you have a CAS file which is at least 16384 bytes in size, please refrain from posting trollish things.
  15. That's almost never all that's needed. How often did people tell you to post the complete project? Why can't you learn?
  16. use _sys() https://cc65.github.io/doc/funcref.html#ss3.14
  17. you always with just sending snippets, sigh try .word __XBUF__START__+__XBUF__SIZE__-1
×
×
  • Create New...