[Coco] Some details on CoCo 1 ROM burning

[Charles Hudson]

Well, my screenshot bounced but the gist of it is: binary.

On 12/18/2021 12:41 PM, Dave Philipsen wrote:
> I’m not sure what format the files you acquired are (probably binary) but you can verify by trying to open them with a text editor. Intel Hex usually have lines that start with a colon and a hex number (i.e. :20). Intel S records usually have lines that start with ‘S1’ followed by some hex numbers. Binary files will just show up as a bunch of garbage in a text editor.
>
> As far as programming the EPROMs, yes, a starting address of 0000 and the hardware will decode it to the proper address in the 6809 memory map.
>
>
>> On Dec 18, 2021, at 6:37 AM, Charles Hudson <charles484 at twc.com> wrote:
>>
>> As described earlier I have a CoCo 1 which came with Color Basic 1..1 in ROM and I am interested in fitting a TCDD controller and drive to the system.  Accordingly I need to upgrade the ROMs and add Extended Color Basic.
>>
>> I have obtained MCM68766C35 EPROMs, blanked them, obtained a Needham's EMP-20 programmer and the DOS software, verified the parallel port operation of the EMP-20 with a '586 VLB machine and downloaded the CoCo ROM images from Tandy Color Computer Archive. I plan to use at least CB 1.2 and ECB 11.  I know the ECB ROM goes in the higher-numbered IC slot, left if facing from the front.
>>
>> Now I come to actually programming the EPROMs and two questions occur to me:  Which format are these ROM images?  Binary, Intel hex and Motorola S hex are possibilities (among others); I would assume Motorola hex format for these.  And should I load each ROM image with a 00 starting address in the ROM and let the hardware sort out the addressing?
>>
>> Just checking...  Thanks for your replies.
>>
>> -CH-
>>
>>
>> -- 
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>