Comments (4)
EtchedPixels
commented on July 17, 2024
Had me puzzled for a bit as it ran perfectly well on my RC2014 6803 box (albeit without video at that address)
Turns out to be a mix of environment and set up problems not the compiler itself
- The MC10 has no RAM at 0x20-0x7F (moved it to 0x90)
- The crt0 code was not clearing BSS and setting up direct page values needed (added)
With those two fixed it seems to behave nicely. I've also updated the setup so the MC10 has its own crt0 (initial pre C code)
from cc6303.
jggames
commented on July 17, 2024
Dear Fabrizio,
Sorry I’m just a Basic coder. Your question is above my pay grade. The only thing I’d note is the MC-10 has a 6803 (not 6303). I was under the impression there is no working C compiler for it. I’d ask Greg Dionne or James Tamer on the MC-10 facebook group. They’re the machine code gurus.
Jim
Sent from Mail for Windows 10
From: Fabrizio Caruso
Sent: Friday, June 4, 2021 10:39 AM
To: EtchedPixels/CC6303
Cc: Subscribed
Subject: [EtchedPixels/CC6303] [bug] Probably wrong arithmetic (#4)
I am compiling a simple program that is supposed to fill the screen with screen code 67 ('C' on many systems include the MC-10):
#if defined(__MC10__)
#define SCREEN 0x4000
#define YSize 16
#define XSize 32
#elif defined(__C64__)
#define SCREEN 0x0400
#define YSize 25
#define XSize 40
#elif defined(__VIC20__)
#define SCREEN 7680
#define YSize 23
#define XSize 22
#endif
#define POKE(addr,val) (*(unsigned char*) (addr) = (val))
#include <stdint.h>
#include <stdio.h>
int main(void)
{
uint8_t i;
uint8_t j;
for(i=0;i<YSize;++i)
{
for(j=0;j<XSize;++j)
{
POKE((uint16_t) SCREEN+((uint16_t)i)*XSize+j,67);
}
}
while(1){};
return 0;
}
I compile it with CC65 and CC6303 with something like:
mc10_test:
cc68 -tmc10 -D__MC10__ $(SOURCE_PATH)/../../test/mc10_test1.c -o $(BUILD_PATH)/$@
vic20_test:
cl65 -tvic20 -D__VIC20__ $(SOURCE_PATH)/../../test/mc10_test1.c ***@***.***
c64_test:
cl65 -D__C64__ $(SOURCE_PATH)/../../test/mc10_test1.c ***@***.***
It works fine on both the C64 and VIC20 but on the MC10, it just fills half the screen as if there were some sort of overflow:
I have attached the MC10 binary and the .c10 file
build.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
from cc6303.
Fabrizio-Caruso
commented on July 17, 2024
Hi
This has just been fixed by Alan Cox.
I never said the MC-10 has a 6303. CC6303 is the name of the project.
Fabrizio
--
Sent from myMail for Android Saturday, 05 June 2021, 01:22AM +02:00 from Jim Gerrie ***@***.*** :
…Dear Fabrizio,
Sorry I’m just a Basic coder. Your question is above my pay grade. The only thing I’d note is the MC-10 has a 6803 (not 6303). I was under the impression there is no working C compiler for it. I’d ask Greg Dionne or James Tamer on the MC-10 facebook group. They’re the machine code gurus.
Jim
Sent from Mail for Windows 10
From: Fabrizio Caruso
Sent: Friday, June 4, 2021 10:39 AM
To: EtchedPixels/CC6303
Cc: Subscribed
Subject: [EtchedPixels/CC6303] [bug] Probably wrong arithmetic (#4)
I am compiling a simple program that is supposed to fill the screen with screen code 67 ('C' on many systems include the MC-10):
#if defined(__MC10__)
#define SCREEN 0x4000
#define YSize 16
#define XSize 32
#elif defined(__C64__)
#define SCREEN 0x0400
#define YSize 25
#define XSize 40
#elif defined(__VIC20__)
#define SCREEN 7680
#define YSize 23
#define XSize 22
#endif
#define POKE(addr,val) (*(unsigned char*) (addr) = (val))
#include
#include
int main(void)
{
uint8_t i;
uint8_t j;
for(i=0;i {
for(j=0;j {
POKE((uint16_t) SCREEN+((uint16_t)i)*XSize+j,67);
}
}
while(1){};
return 0;
}
I compile it with CC65 and CC6303 with something like:
mc10_test:
cc68 -tmc10 -D__MC10__ $(SOURCE_PATH)/../../test/mc10_test1.c -o $(BUILD_PATH)/$@
vic20_test:
cl65 -tvic20 -D__VIC20__ $(SOURCE_PATH)/../../test/mc10_test1.c ***@***.***
c64_test:
cl65 -D__C64__ $(SOURCE_PATH)/../../test/mc10_test1.c ***@***.***
It works fine on both the C64 and VIC20 but on the MC10, it just fills half the screen as if there were some sort of overflow:
I have attached the MC10 binary and the .c10 file
build.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or unsubscribe .
from cc6303.
jggames
commented on July 17, 2024
Dear Fabrizio,
Sorry. Just flailing in the dark. Didn’t notice that the message was just a feed from Github (hadn’t seen anything for while from Alan’s compiler repo) until after I had replied. Have read over your threads now. Good to see you’re both making progress. I’ll slip back into the shadows now…
Jim
Sent from Mail for Windows 10
From: Fabrizio Caruso
Sent: Friday, June 4, 2021 8:28 PM
To: EtchedPixels/CC6303
Cc: Jim Gerrie; Comment
Subject: Re: [EtchedPixels/CC6303] [bug] Probably wrong arithmetic or cast (#4)
Hi
This has just been fixed by Alan Cox.
I never said the MC-10 has a 6303. CC6303 is the name of the project.
Fabrizio
--
Sent from myMail for Android Saturday, 05 June 2021, 01:22AM +02:00 from Jim Gerrie ***@***.*** :
Dear Fabrizio,
Sorry I’m just a Basic coder. Your question is above my pay grade. The only thing I’d note is the MC-10 has a 6803 (not 6303). I was under the impression there is no working C compiler for it. I’d ask Greg Dionne or James Tamer on the MC-10 facebook group. They’re the machine code gurus.
Jim
Sent from Mail for Windows 10
From: Fabrizio Caruso
Sent: Friday, June 4, 2021 10:39 AM
To: EtchedPixels/CC6303
Cc: Subscribed
Subject: [EtchedPixels/CC6303] [bug] Probably wrong arithmetic (#4)
I am compiling a simple program that is supposed to fill the screen with screen code 67 ('C' on many systems include the MC-10):
#if defined(__MC10__)
#define SCREEN 0x4000
#define YSize 16
#define XSize 32
#elif defined(__C64__)
#define SCREEN 0x0400
#define YSize 25
#define XSize 40
#elif defined(__VIC20__)
#define SCREEN 7680
#define YSize 23
#define XSize 22
#endif
#define POKE(addr,val) (*(unsigned char*) (addr) = (val))
#include
#include
int main(void)
{
uint8_t i;
uint8_t j;
for(i=0;i {
for(j=0;j {
POKE((uint16_t) SCREEN+((uint16_t)i)*XSize+j,67);
}
}
while(1){};
return 0;
}
I compile it with CC65 and CC6303 with something like:
mc10_test:
cc68 -tmc10 -D__MC10__ $(SOURCE_PATH)/../../test/mc10_test1.c -o $(BUILD_PATH)/$@
vic20_test:
cl65 -tvic20 -D__VIC20__ $(SOURCE_PATH)/../../test/mc10_test1.c ***@***.***
c64_test:
cl65 -D__C64__ $(SOURCE_PATH)/../../test/mc10_test1.c ***@***.***
It works fine on both the C64 and VIC20 but on the MC10, it just fills half the screen as if there were some sort of overflow:
I have attached the MC10 binary and the .c10 file
build.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or unsubscribe .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
from cc6303.
Related Issues (16)
- [info] How to use? Can it be used for the TRS-80 MC-10? HOT 33
- [info/bug?] How do I build the compiler? make all fails under Windows/Cygwin HOT 2
- [bug] Arrays seem to return their index HOT 1
- [bug] Broken Conditional or assignment HOT 2
- [bug?] make clean does not clean libs and other files. Is it wanted? HOT 2
- [question] Assembly and C? HOT 7
- 6800 build generates a relocation failure when building Fuzix "dc"
- libc.a is 0 byte HOT 12
- [bug?][right shift] Right shift operator produces broken binary HOT 4
- [feature request] Future support for the TMS9900? (if possible with minimal lib for the TI99/4A?) HOT 11
- [question/feature] Where is the MC10 code located by default? HOT 8
- Issue with little CRC-16 program compilation? HOT 9
- [Question] HOT 6
- Syntax errors with conditional jumps HOT 1
- Cassette file produced by Tapify gets me ?FM Errors HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cc6303.