Jump to content

Zakero

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Thanks for the clarification, I can load images now!
  2. In the Commander X16 Programmer's Reference, the section LOAD into VRAM explains how to load data directly into VRAM using Basic. Is there an equivalent for assembly? If this functionality is currently unavailable, it would be nice if SETLFS's Register Y value could be used in the same manner as described for Basic. Example: ldx #$08 ; Default to Device 8 ldy #$03 ; Set Address to $10000 + (first 2 bytes of file) jsr SETLFS
  3. Thank you everyone for looking into and fixing the issue, I will be looking forward to the next release! Also, thank you @Greg King for modifying the LOADDATA code! I will be putting in some time to understand those changes and their effects.
  4. Thank you clarifying that the 2-byte file header must be always present! I am sure that knowledge just saved me from some future grief Yes, my data file is really called "DATA", all caps. You could probably guess that my program is called "LOADDATA"... The data file was updated to have the 2-byte header with the address of $3000. The code was not changed, so it is still hard-coded to use the $2000 address. Upon re-running the data was loaded to $3000. Not the $2000 specified in the program.
  5. Wrote a short assembly program to load a file into memory address $2000 but the file is not being placed in the expected address. The file contains 256 bytes with a value of #$11. All 256 bytes are #$11. This was to make it easier to see where the file was loaded into RAM. The expected address to find the data was $2000, however the file was loaded at $1111. It was my understanding that when setting up the Logical File, I could set the Secondary Address to (LDY) #$00 for a relocated load. When loading the file, I would then specified the $2000 address. If I had set the Secondary Address to (LDY) #01, then I would expect the first two bytes of the file to be used the destination address. This does work. But hard-coding the destination address does not work. Below is my code, if that would help clarify what I am talking about. Can someone enlighten me as to what I am doing wrong or misunderstanding? ; ca65 formatted code .pc02 load_file: ;--------------------------------------- ; Set the file name lda #(filename_end - filename) ldx #<filename ldy #>filename jsr $ffbd ; KERNAL::SETNAM ;--------------------------------------- ; Setup the logical file to use lda #$01 ; The File ID to use ldx #$08 ; Device 8 = Disk Drive ldy #$00 ; Secondary address of 0 jsr $ffba ; KERNAL::SETLFS ;--------------------------------------- ; Load the file lda #$00 ; load to memory (1 = verify) ldx #$00 ; at address $2000 ldy #$20 jsr $ffd5 ; KERNAL::LOAD ;--------------------------------------- ; Did it work? bcc all_good stp ; Break into the debugger ; Register A has the error code all_good: stp ; File loaded at $1111 instead of $2000 filename: .byte $44,$41,$54,$41 ; DATA filename_end:
  6. Is there enough room in the ROM to add support for the US Dvorak keymap (10409)? After a little peek'ing around the ROM repository, it looks easy enough to do. Are there other factors preventing this keymap addition?
×
×
  • Create New...

Important Information

Please review our Terms of Use