-
The compilation of the current source presents the following warning for targets with Motorola 6809 processor and active optimization:
src/targets/d32/_optimizer.c: In function ‘vars_remove’:…
-
The compilation of the current source presents the following warning for targets with Motorola 6809 processor and active optimization:
src/targets/d32/_optimizer.c: In function ‘tmp_buf’:
…
-
some target files do not get built.
If i try to xl build all coco, getting a lot of missing targets for this system, compared to c64 system.
I tried xl build all all and get better resaults.
coco d…
ghost updated
2 years ago
-
When using PROGMEM_SECTION other than 0, I get verification errors.
Using PROGMEM_SECTION1:
pymcuprog.programmer - ERROR - Verify failed: Verify mismatch starting at location 0x008000: 0x07 vs 0xF…
-
While testing examples/maths_example_02.bas, where I got wrong result I came along this one-line code:
`PRINT 3*3*3`
It prints 0 on the MO5/PC128op, and may be on other platforms. Of course this isn…
-
Once put to work, the compiler proves to be inefficient from the point of view of the space occupied.
In fact, if we exclude the need to introduce portable mechanisms to differentiate the data memo…
-
Hi David,
I am new to touchscreens.
I am using a blue mcufriend 2.8 inch (ili9338 silkscreened on PCB) purchased from Banggood with your button_simple.ino sketch on a UNO R3.
After using TouchScr…
-
I am interested in NES, SNES, PCE and the Sega Genesis.
-
The cpu tests are currently structured for executing on a 6809 itself - but that is the only method of execution, if you want to test under emulation, you have to emulate a system that supports these …
gtoal updated
3 years ago
-
Greg,
I noticed that the following command, which is just supposed to creation an oscillating value between 0 and 1 actually returns -65535 when it should return a 0:
F=-(F=0)
In other words,…