 |
|
 |
| Parallax Forums > Public Forums > Propeller Chip > TriBladeProp PCB: Uses 3 Propeller ICs for a Single Board Computer (SBC) | Forum Quick Jump
|
|  TrapperBob Registered Member
        Date Joined Sep 2004 Total Posts : 38 | Posted 9/17/2009 9:27 AM (GMT -8) |   | Dr_Acula:
I have had a triblade up an operational for several months. I have been following the thread development without updating from earlier release. I believe the release was around rr80 ? So I know how to format and SD card and the hardware necessary to do so. I have just found throughout the life of this development that the filenames in the published zip archives have routinely changed names. That seems to have been somewhat rectified. As I stated earlier having processes scripted lends to their documentation and the ability for new folks to catch on faster in my opinion.
Cluso99: I appreciate your info on non-relevance of order( I was not sure!) and I will create an example script (.bat file) to automate this process in the future once I am sure I fully understand. I do believe as you (we) get closer to a V1.0 release many of these vagarities will disappear. In one of the latest SD file zip files there was a .PTR file. Does this or should this be written to the SD card? I also saw a ZICOG_A2.dsk and ZIPM2_64.DSK. What is the use for ZICOG_A2.dsk? These are the types of things some of the newer folks may struggle with understanding. | | Back to Top | | |
 |  Cluso99 We live onboard

       Date Joined Apr 2008 Total Posts : 2276 | Posted 9/17/2009 7:11 PM (GMT -8) |   | BoB: The .PTR file is not used. I made this for heater so he could possibly use it in his 25K prop demo board. re the filenames... If you look at the ZiCog_cpm... (previously called ZiCog_demo...) spin file there is a routine called FindSDblock. This section list all the SD files that will be used in this version, including what drives they will be mapped to.
It is necessary to keep changing filenames when they become incompatible with the older versions of code. This is so I can run older versions of the code, together with the latest.
As you can see, there is a problem heater and drac are working on which will mean a new A: drive disk file when they fix the bug.
ZICOG_A2.DSK was to be the default name of the A: disk file with 2=CMP2.2 However, that file was only a version for 25K of user space (ram). Heater produced a new version with 64K of user space called ZIPM2_64.DSK so this is currently mapped as the A: drive - it has a bug so it's name will change when fixed.
Drac: Can we keep filenames "ZICOG_dv.DSK" where d=normal drive no (A:...H:), v=CPM/MPM version (0=not specific, 2=CPM2.2, 3=CPM3, M=MPM) ? This way we can change the A: drive boot disk to vary from CPM2.2, CPM3 (banked, etc), MPM, etc For drives with wordstar, vedit, etc, we could use "WORDSTAR.DSK", "VEDIT .DSK", "C .DSK", "BASIC .DSK", etc Does this make sense??? Links to other interesting threads:
| | Back to Top | | |
     |  Dr_Acula Registered Member

       Date Joined Dec 2008 Total Posts : 606 | Posted 9/19/2009 11:29 PM (GMT -8) |   | After a late night email brainstorming session with Cluso last night, I've realised that I haven't removed pin 24 of the ram chip and installed a wire link. So when I get home I'll need to do this. It is surprising it works, as this is the /RD (or /OE) pin. I think it does work because there is a feature of the ram chips with a low on /RD and /WR at the same time does a write, even though this isn't a valid condition using the old-school Z80 type bus.
I'm pondering adding one more latch for another 8 output pins and even another latch for 8 inputs. Maybe poll these which you could do every few instructions and that would be quick enough to do some more (slower?) serial ports and poll a keyboard. Eg set all the inputs such that they default to high using pullups and then read in a byte and if any bit is low, ie the byte is <>255, go off and process it, but otherwise the regular checking doesn't add much overhead.
Crazy idea here - but add one 573 and use 6 pins to drive a LCD display, and 2 to drive two serial ports. On the input chip, use two pins to poll serial ports and two to poll a keyboard. 4 spare. Put the input latch into the data lines, and put the second output latch on A8 to A15. Then with two extra chips (and maybe a max232) but no mods to the existing circuit, it could do an LCD display, keyboard and two serial ports. That would be a nifty self contained computer with just one propeller.
Meanwhile, the world has run out of DIP propellers and so if one has to look at surface mount, this got me looking at ram chips and I found this interesting one from futurlec http://www.futurlec.com/Memory/628512LLFP-70.shtml which is low voltage, surface mount and it would be great if this worked as it is $8.40 and futurlec's standard shipping for small orders is $4 worldwide.
Tonight I will do that wire link and then maybe do a quick schematic with two more latches. Maybe surface mount for all?? www.smarthome.viviti.com/buildPost Edited (Dr_Acula) : 9/20/2009 8:02:40 AM GMT | | Back to Top | | |
   |  Dr_Acula Registered Member

       Date Joined Dec 2008 Total Posts : 606 | Posted 9/20/2009 2:05 AM (GMT -8) |   | Hi Cluso,
I'm partly posting this because I still don't quite understand the modifications, and partly to help others who still haven't got a triblade working. I hope this is ok.
This photo shows your board with one ram installed www.bluemagic.biz/clusodocs/tribladeprop_a1d.jpg This photos shows the modification with description www.bluemagic.biz/clusodocs/tribladeprop_a1b.jpg This photo shows your schematic before any mods www.bluemagic.biz/clusodocs/tribladeprop_sch_375p2.bmp This photo shows a modification to a two ram chip triblade http://www.bluemagic.biz/clusodocs/tribladeprop_a1c.jpg Attached is my attempt in Eagle to redraw the schematic.
Ok, from the description in your email, you said "SO THE MODIFICATION REQUIRED TO REMOVE /OE FROM GND AND TIE TO P28 (SCL) WAS REQUIRED"
This is the modification I see on the two ram solution. But not mentioned on the one ram solution.
Let's look at a one ram board for the moment: Is the following correct?
1) Disconnect ram pin 24 from ground (lift the pin out of the socket) and connect it to physical pin 37 of the propeller (a line variously called CLK, SCL or P28 depending on the chip. I've called it CLK on my schematic)
2) Join ram pin 22 of the ram chip to pin 11 of the 573 (which is the wire link from pin 11 to pin 17 of the 573). Leaving aside the brief potential data conflict on the latch, this means that pin 22 of the ram chip (/CE or /CS) is now driven by physical pin 36 of the propeller.
I *think* the source of the confusion is not mod #1, but that mod #2 applies to 1 ram chip boards as well as 2 ram chip boards.
If the above is all correct, could I then ask whether, instead of putting the mod #1 with an output of a latch potentially feeding back into its own latch input, whether you could lift pin 24 of the ram chip and put a wire link to pin 11 of the latch (or to pin 37 of the prop). www.smarthome.viviti.com/buildPost Edited (Dr_Acula) : 9/20/2009 11:11:43 AM GMT
File Attachment : Triblade_rename_pdf.txt 47KB (text/plain)This file has been downloaded 12 time(s). | | Back to Top | | |
     |  Cluso99 We live onboard

       Date Joined Apr 2008 Total Posts : 2276 | Posted 9/20/2009 4:37 AM (GMT -8) |   | | | |
   |  Dr_Acula Registered Member

       Date Joined Dec 2008 Total Posts : 606 | Posted 9/20/2009 5:00 AM (GMT -8) |   | | | |
   |  Dr_Acula Registered Member

       Date Joined Dec 2008 Total Posts : 606 | Posted 9/20/2009 6:02 AM (GMT -8) |   | Going off on a tangent, one of the things I've found invaluable when writing actual CP/M code is some sort of integrated development environment. I'm very excited to announce that with the latest speedups that Heater and Cluso have managed to make, the IDE for the N8VEM now also works for the Zicog. This is a terminal program amongst other things, but it also allows downloads of packages of files, using a fast version of xmodem called xmodemf.com
So - I used teraterm to download xmodemf.com using the propeller version xmodemp.com.
Now one can send all the wordstar package, or the sbasic package in one go. So easy!
Better still, one can use the IDE for sbasic or BDSC or Assembly, with the copy and paste function and the coloured code etc.
And, it compiles on the board. And it is FAST!!! This is a screen capture of the program running on the triblade. Ok, I cheated a little and wrote the actual program on the PC using the N8VEM IDE (though I could have written it using notepad, or even wordstar [very soon once that bug is squisheed] on the triblade).
A>type new.bas
comment call small procedures first then bigger procedures as can't call/reference a later procedure (one pass compiler) Dim common variables eg arrays at beginning of program end rem *** functions and procedures ***
rem ************ MAIN **************
print "Hello World" end
A> A>sbasic new
tm S-BASIC Compiler Version 5.4b
.0001:00 comment 0002:01 call small procedures first then bigger procedures 0003:01 as can't call/reference a later procedure (one pass compiler) 0004:01 Dim common variables eg arrays at beginning of program 0005:01 end 0006:00 rem *** functions and procedures *** 0007:00 0008:00 rem ************ MAIN ************** 0009:00 0010:00 print "Hello World" 0011:00 end 0012:00 ****** End of program ****** ...........................Compilation complete
A>new
Hello World
A>
www.smarthome.viviti.com/build
Image Attachment :
 image2.jpg 82KB (image/jpeg)This image has been viewed 14 time(s). | | | |
| | Back to Top | | |
     | 849 posts in this thread. Viewing Page : | | Forum Information | Currently it is Friday, November 20, 2009 11:12 PM (GMT -8) There are a total of 393,738 posts in 55,521 threads. In the last 3 days there were 82 new threads and 702 reply posts. View Active Threads
| | Who's Online | This forum has 17687 registered members. Please welcome our newest member, mark09. 48 Guest(s), 2 Registered Member(s) are currently online. Details BradC, SRLM |
Forum powered by dotNetBB v2.42EC SP2.02 dotNetBB © 2000-2009 |
|
|