
togster510
Members-
Content Count
14 -
Joined
-
Last visited
-
Days Won
1
togster510 last won the day on July 10 2020
togster510 had the most liked content!
Community Reputation
10 Good-
togster510 started following X16 Official Announcements
-
togster510 started following Vera debugging, Who would like to participate in an x16 game jam?, What is the kernel call to check if there is a character? and and 2 others
-
What is the kernel call to check if there is a character?
togster510 replied to BruceMcF's question in X16 Programming Support
GETIN ($FFE4) returns zero if there are no characters in the keyboard buffer, I think. Sent from my iPhone using Tapatalk -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
In that routine, you could also consider handling return characters, which don’t have a screen code but would allow you to have longer bits of text. Sent from my iPhone using Tapatalk -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
There is also https://style64.org/petscii/ which is good for exploring the relationships between different character encodings Sent from my iPhone using Tapatalk -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
That I think is the problem. When writing directly to vera you need to use screencodes rather than petscii values. However, PRINT uses petscii. For a discussion of this, see https://retrocomputing.stackexchange.com/questions/7529/why-the-disparity-between-the-screencodes-and-the-character-codes . The assemblers I've tried have all had a mechanism to translate text to screencodesfor you, but I couldn't find documentation for c64 studio (which I believe is what you're using). Maybe search in the help for screencodes and see what you can find. -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
Could you try changing the !text directive to !scr ? Sent from my iPhone using Tapatalk -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
How are you getting the text into ram? I suspect it's an encoding problem. -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
Also, typing ‘m A134’ in the debugger will show the memory values in the lower section. Sent from my iPhone using Tapatalk -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
Could you post what it is supposed to say? Sent from my iPhone using Tapatalk -
assembly variables / two byte memory addressing
togster510 replied to JohnGill's question in X16 Programming Support
The 6502 is little endian. This means that when using a 16 bit number (like an address) it expects the 'low' byte to come before the 'high' byte in memory. So you need to swap some bytes round. For your example, you should have startLo = $14, startHi = $15, then lda (startLo),x. Hope that helps. -
Thanks for the info.
-
Quick question: is it possible to view the contents of vram in the debugger? If so, how? Sent from my iPhone using Tapatalk
-
togster510 started following X16 Programming Support
-
togster510 started following Hello World assembly beating me!
-
Hello World assembly beating me!
togster510 replied to JohnGill's question in X16 Programming Support
There is a system function listed in the programmer's reference called screen_set_charset to do exactly this. LDA #3 and then JSR $FF62 will switch to PET upper/lower. -
I think what many people called it this year was either ‘pub reopening day’ or ‘haircut day’ Sent from my iPhone using Tapatalk