[Coco] Just another peek...

Fri Oct 9 23:42:27 EDT 2015

I'm just thinking out loud. Just figured if you can make a rommable system then it couldn't be that difficult to load the system in one fell swoop. No, I agree.  You wouldn't want to lock out all that stuff unless it was embedded.

Dave Philipsen

> On Oct 9, 2015, at 9:44 PM, Bill Pierce via Coco <coco at maltedmedia.com> wrote:
> 
> Dave, it sounds like you're off to a good start. I wish I knew more about SD cards and could help.
> I do have one question...
> You mentioned locking out the boot memory essentually making it a rom.. Why?
> This makes it impossible to modify modules (in memory) and "cobblering" a new boot. It also locks out "Xmode", "tmode", "dmode>, and "wmode" from changing descriptors on the fly.
> I'm not protesting, just wanting to know the reasoning behind locking the memory. Or am I misinterpreting your post?
> 
> 
> 
> 
> 
> 
> Bill Pierce
> "Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull
> 
> 
> 
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> Global Moderator for TRS-80/Tandy Color Computer Forums
> http://www.tandycoco.com/forum/
> 
> E-Mail: ooogalapasooo at aol.com
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Dave Philipsen <dave at davebiz.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Fri, Oct 9, 2015 7:59 pm
> Subject: Re: [Coco] Just another peek...
> 
> 
> Oh and, by the way, I'm definitely not knocking drivewire.  It certainly 
> has
> its place and its functions are much more than just a 'disk 
> controller' but the
> SD card on the CoCo3FPGA is an order of magnitude 
> faster than drivewire running
> at 115.2kbps.  And rightfully so as its 
> SPI interface is running at a frequency
> that is an order of magnitude 
> higher than a typical serial port. It is
> especially noticable when 
> you're doing disk intensive operations like
> assembling or compiling 
> programs.
> 
> 
> Dave
> 
> 
> On 2015-10-09 17:49, tim
> franklinlabs.com wrote:
>> That makes sense. I was looking at the Atari 800 SOC
> for the DE1 and
>>   they did the same thing. Thanks for clarifying that.
> On October 9, 2015 at 3:39 PM Dave Philipsen <dave at davebiz.com>
>>     wrote:
> The wires that can be added are not a requirement. The DE1 
>> evidently
> neglected to connect the card insertion switch. So if you want
>>     NitrOS9
> to automatically detect when you have removed the card or
>>     'hot-plugged'
> a new one in then you need the wires. I have personally run the SD
>>     card
> successfully under NitrOS9 without any wires. In that condition 
>> it's
> best that you regard the SD card as non-removable unless you shut
>>     OS9
> down.
>>     As I mentioned before the access to the SD card is not yet
> integrated
>>     into DECB. The card does work in that environment but you must
> 
>> write
>>     your own 'driver'. I have personally used code to access
> sectors
>>     (reading and writing) from the DECB environment. In fact, I
> already
>>     have the core of a program that can manage multiple 'partitions'
> 
>> on
>>     the
>>     SD card and make them available for booting from DECB.
> Dave Philipsen
>>>     On 2015-10-09 15:21, tim franklinlabs.com wrote:
> From what I understand (from the documents) the SD card only 
>> works
> with
>>> Nitros9 and requires a wire to be added (not sure about the wire
>> 
>> thing). Everything I read states it doesn't work with DECB (yet!
> maybe?)
>>> 
>>> On October 9, 2015 at 1:27 PM Michael Brant
> <brant.michael.l at gmail.com> wrote:
>>> I am also interested in knowing more
> about the SD card access as 
>> i
>>> would
>>> want a stand alone
> setup.
>>> On Oct 9, 2015 2:24 PM, "Barry Nelson"
> <Barry.Nelson at amobiledevice.com>
>>> wrote:
>>>> I would want one of
> these, but I do not want to have to use an
>>> external
> DriveWire server. Any updates on how the SD card access is
>>> going?
>> 
>>> 
>>>> 
>>>> 
>>>>> Dave Philipsen dave at davebiz.com
>> 
>>> 
>>>>> Fri Oct 9 10:51:34 EDT 2015
>> 
>>>> It works just like the other video modes on the CoCo 3. The
> video
>>>> memory is part of the 512k memory map. In this case about
>> 
>> 288,000
>>> bytes of
>>>> memory are used.
>> 
>>> 
>>>>> Dave Philipsen
>>>> 
>>>> 
>>>> 
>>>> O/
> On Oct 9, 2015, at 1:45 AM, Brett Gordon <beretta42 at
>>> gmail.com>
>> 
>>> wrote:
>>>> 
>>>> 
>>>> O/ That's awesome
> Dave! So where exactly is this video memory
>>> coming from?
>> 
>>> O/ ahhh.. i really want one of these now...
>>>> 
>> 
>>> 
>>>> O/ --
>>>> 
>>>> O/ Coco mailing list
>> 
>>> O/ Coco at maltedmedia.com
>>>> 
>>>> O/
> https://pairlist5.pair.net/mailman/listinfo/coco
>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>>> --
> Coco mailing list
>>> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>>     --
>>     Coco mailing
> list
>>     Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
> 
> -- 
> Coco mailing
> list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
> 
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco