|
Post by cthulhu on May 11, 2015 12:18:47 GMT
Ok, so I finished building it and hooked it up to my TV. Seems one of my resistor values was a little off and the "dark" colours are too dark. I can tweak that easily though. Here is a photo of the C128 hooked directly to the SCART input of my modern Samsung HDTV. postimg.org/image/s7c8h1yr7/Wow! Color code 10 should be the in-famous "Brown", right? It looks pretty good, even with your current dark setting! I haven't looked at the schematics, did you manage to put some sort of "brown-fix" circuit on the board? I would be interested, depending on the price of the assembled unit and if you plan to ship it with a full cable harness: I hate making those by myself!
|
|
|
Post by cthulhu on Mar 26, 2015 7:57:37 GMT
How do you transfert your program from PC to the Commodore? You use directly your SD2IEC? Yes. Basically, the SD2IEC is an SD card reader for your Commie: you just fill the SD using your PC and put it back, when ready, into the SD2IEC.
|
|
|
Post by cthulhu on Feb 24, 2015 12:57:50 GMT
Heh, I did not include the C128 p.s., because it is not sealed, and thus it is repairable. Those sold in Europe were "almost sealed": there's a screw in the bottom, but you need to drill through some plastic to reach it.
|
|
|
Post by cthulhu on Jan 16, 2015 10:00:37 GMT
I can confirm what hydrophilic said, it's probably only a MMU config issue.
|
|
|
Post by cthulhu on Jan 15, 2015 8:38:11 GMT
Sadly must to say that VICE works not. At least v2.4 and newer. I'm using VICE 2.4.6 under linux / x86_64 and it works. If you will, post here youre ROM binary and I'll give it a try.
|
|
|
Post by cthulhu on Jan 14, 2015 10:45:57 GMT
I'm doing this a little differently (for an internal function ROM):
*= $8000 ; ; Function ROM Header ; jmp start ; Cold start entry point (3 bytes long) .byt $d2 ; Warm start (3 bytes long) .byt $d7 .byt $d7 .byt $b4 ; ROM ID .asc "cbm"
Routine at start prints a welcome message and binds a menu of options to the HELP key (basically it's a list of programs in ROM which are then copied to RAM and executed).
|
|
|
Post by cthulhu on Nov 27, 2014 8:43:39 GMT
Another thing that got me thinking is the company is called "Microbee Technology". I seem to remember a company by that name (or very similar) back in the '80s and '90s... is it the same company that made CBM products back in the day? If so, it is amazing they have survived and continue to support CBM technology!! I don't know about them making CBM products, but here is their history. By the way, Australia's (Microbee's home country) (analog) TV standard is PAL B/G, so if they commercialize a product based on the GBS-8200 it should work, right?
|
|
|
Post by cthulhu on Nov 24, 2014 9:40:24 GMT
|
|
|
Post by cthulhu on Oct 29, 2014 15:45:30 GMT
I don't think the internal battary could be the culprit here: its purpouse should be to keep the clock running when power is off, what I'm experiencing is that I'm not abale to operate the clock at all. I mean, after setting the correct time I should be able to subsequently read incrementing time values, but I'm not. By the way, this is the code for a small library to set and read time from the SmartWatch:
.word $1300 *= $1300 ; ; DS1216E operation addresses ; ra = $8004 rw0 = $8000 rw1 = $8001 ; ; User I/O buffer ; buffer .dsb 8,$00 ; ; User subroutins vector ; jmp read jmp write ; ; Activation pattern ; pattern .byt $c5,$3a,$a3,$5c,$c5,$3a,$a3,$5c
reset .( ldx #$40 loop lda ra dex bne loop rts .)
open .( jsr reset sei ldy #0 ldx #8 loopy lda pattern,y sta $fe loopx lda $fe and #$01 bne write1 lda rw0 jmp next write1 lda rw1 next nop nop lsr $fe dex bne loopx iny cpy #8 bne loopy cli rts .)
read .( lda $ff00 pha lda #$06 sta $ff00 jsr open sei ldx #0 loopx ldy #8 loopy lda ra nop nop lsr rol buffer,x dey bne loopy inx cpx #8 bne loopx cli pla sta $ff00 rts .)
write .( lda $ff00 pha lda #$06 sta $ff00 jsr open sei ldy #0 ldx #8 loopy lda buffer,y sta $fe loopx lda $fe and #$01 bne write1 lda rw0 jmp next write1 lda rw1 next nop nop lsr $fe dex bne loopx iny cpy #8 bne loopy cli pla sta $ff00 rts .)
|
|
|
Post by cthulhu on Oct 24, 2014 12:31:06 GMT
[...] my Qs to users are simple - use old look (faster release, but many functions never available) or new look (release later, support of all fns - maybe not in first release, but without changes later). I need feedback. Miro I'd say: go for the new look! In my experience developing software while knowing that some functionalities are outdated and that they very likely should be rewritten in the future only to release it earlier is a bad decision in the long run.
|
|