Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Powertran Cortex

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    As to the wiring changes, when doing the schematic and PCB I was confused over the numbering of the '612 pins (I forgot that TI numbers in reverse order, also on 74-series chips). Also tying the unused mapper lines together is not the best practice, although it doesn't hurt. The fix is:
    - Separate pin 12, 29, 30 and 31.
    - Cut wire from pin 14 of the mapper to pin 28 of the RAM
    - Add a wire from pin 24 on the mapper to pin 28 of the RAM
    - Add a wire from pin 7 on the mapper to pin 31 on the mapper

    74LS612 chips get quite hot (I guess they are run at high currents to get minimal delay times with the chip technology of the time). Personally I prefer 74HCT612 chips that draw only a fraction of the power.

    Attached is the current programming info for the GAL (added .txt to get the forum to accept it).

    Paul
    Attached Files

    Comment


      Paul,

      Didn't we conclude that there was a problem using the 74LS612 mapper chip, and it needs to be the HCT version?

      Stuart.

      Comment


        Yes and no.

        There was an issue with the "write protect" bit, that was resolved by a GAL change.

        The last bit of the mapped address is used to block writes. If page F is write protected the mapper itself gets write protected as well (this was a poor design decision that needs change on a rev. 2 mini cortex). When setting the write protect bit for page F it stores through and cuts the write short, leading to faulty writes. Also, LS612 mapper outputs can go through random states before settling, putting noise on the write protection line. The HCT612 seems much more well-behaved and the issues do not arise.

        The solution for a LS612 is to make the write protection dependent on being in "user mode" (GAL change) and modifying the write protect bits only when the mapper is not enabled (Unix change).

        We worked on this almost exactly a year ago. Maybe my memory is fading, but the above is what I recall it was.

        Comment


          Paul, Stuart,
          Good to know these comments. I only have 74LS612 chips, so I am going to try out with those on the mini Cortex.

          My FPGA design does not currently implemented the write protect bit, I used the highest bit for chip select between FLASH and RAM. I also made it so that when the 74LS612 "equivalent" circuit in the FPGA is being addressed (i.e. the "chip select" is active), the mapper itself goes into passthrough mode. I did that originally to keep the design small and to prevent the VHDL code generator from having to make the page registers dual ported, i.e. the address lines of the page registers come either from the low order address lines or high order address lines, not both.
          By the way, about a week ago I debugged the generation of READY signal to get the circuit running at zero wait states. That works also for the Flash memory, despite it being a 120ns part running at under voltage. Maybe I have been just lucky there. When I have time I will measure with the scope the page translation delay.

          Erik

          Comment


            Paul,
            I am glad to report that the Mini Cortex works! Amazingly it worked the first I powered it up with all components mounted. I am using a 64K (E)EPROM, so I needed to fiddle a little on how the memory layout needs to look like to make it look as a 32K ROM for the Cortex CPU. Not difficult though.
            Now I am trying to setup identity memory mapping. I start to understand what your issue on the first PCB was - I first thought that RA12..RA15 would appear at MO0..MO3 when mapper is disabled, but actually that can't be right and it seems they come out from MO11..MO8. So I need to get my head around what the register values need to be in the beginning to enable mapping without changing the memory map.
            I don't think I have much time today, but I am looking forward to working on this!

            Erik


            IMG_4641.jpg

            Comment


              Happy to hear it works for you.

              The wiring fixes leave the map slightly jumbled and the identity map is:
              0,8,1,9,2,a,3,b,4,c,5,d,6,e,7,f
              By this I mean that if you put the above values in the map registers at >FE40 through to >FE4F, it does not matter whether mapping is active or not, as in both cases the same physical memory locations are reached.

              Stuart has done a version of Cortex Basic that works with the mapper as implemented on the mini Cortex (and supports the F18A option as well).

              Let me know when you need MDEX and Unix images.

              Comment


                Thanks Paul.
                Good to know the identity map, I will create a new version of my development firmware to set that up.
                I guess I am ready for the MDEX and Unix images too, I just want do some checks to see that the memory mapper works as I have not been able to fully validate that yet.
                Regarding the CF memory cards, will all sizes work? I may have some old cards laying around somewhere. The new ones seem start from capacities of 8GB or 16GB. I am asking this since now that I've been playing around with SD cards I know there is a communication protocol difference between older and smaller SD cards and newer SDHC cards, so I wonder if there is a similar thing to be aware of for compact flash cards. I know that your boot code requires a FAT32 partition, so that should all be good.

                Comment


                  Originally posted by speccy View Post
                  I guess I am ready for the MDEX and Unix images too, ...
                  Images sent by private mail. Note that the images must be on the card as unfragmented files, so copy them onto a freshly formatted card.

                  Originally posted by speccy View Post
                  Regarding the CF memory cards, will all sizes work?
                  Yes, as far as I know all CF cards support the "memory mode" hardware interface and the few commands that the software actually uses. Note that cards of 2GB and below will not normally be formatted with FAT32. On a Mac "Disk Utility" can be used to reformat. For using both MDEX and Unix the card size needs to be >= 32MB

                  Comment


                    The chap in Germany should be able to rebuild the power supply fairly easily. Even if the transformer's gone away he could replace it with a standard 12-0-12 toroidal one, and wind on the winding for the 5V. It'll probably only be about 20 turns of thickish (about 1mm^2) wire
                    I suppose if the supply is missing completely, a little pc one would do the job with the power control wire shorted to ground to turn it on.

                    Comment


                      SD board for Mini Cortex

                      I've been doing some hardware design over the last several weeks. I had several goals for the whole process - not only to have a working circuit, but also the necessary skills such as experience in PCB design. Today I finally could place an order to sitopway for PCB manufacturing (thanks for the recommendations!).

                      The board is an SD card interface for the Mini Cortex, although I also had other design goals, primarily to have a "universal" SD interface card that would work on many other retrocomputer systems too. As an example I intend to interface it to the TI-99/4A I recently acquired. (That machine is in a pretty beaten up shape and it does not work, so I need to first debug that system too, but it will be another story). I also wanted the board to be useful on a standalone basis too, for development and testing purposes. So in addition to having the obvious SD card interface and the Mini Cortex CF interface, it has a bunch of other extension interfaces too.

                      For the PCB design I wanted to try to do an all SMD design. I have obtained most of the components to see that they match the footprints on the PCB layout. Even though I went with 0805 sized "large" passive components (resistors, capacitors and LEDs), they are pretty darn small. I have test soldered a few TQFP chips by hand on protoboards, and that seems to be doable although my magnifying glass has been heavily necessary. I attach the schematics and PCB layout files for those who are interested. Actually for some reason the PCB pdf file does not want to get attached, the attachment loader shows a red exclamation mark. Any clues? The PDF is 85K in size so it's not huge.

                      It will be interesting to see how the boards turn out and what kind of a nightmare the assembly will be with all this tiny stuff. I am looking forward to the bring up phase after assembly, fingers crossed that the board will work... Waiting mode now. Or actually firmware and VHDL design mode...

                      Erik
                      Attached Files

                      Comment


                        SMD design - ouch! Personally I'd advise through-hole design where possible. Many TI'ers are now of a certain age where hands and eyes are not as good as they once were, and it's likely to put some potential builders off.

                        I see the schematic PDF with lots of lovely interfaces on it. How does one access such a device? Is it all memory mapped ports, or ...?

                        (Trying zipping the file you can't attach, and see if it lets you attach the zip file.)

                        Comment


                          Originally posted by Stuart View Post
                          SMD design - ouch! Personally I'd advise through-hole design where possible. Many TI'ers are now of a certain age where hands and eyes are not as good as they once were, and it's likely to put some potential builders off.
                          Stuart, thanks for the comments. I have to say I am not that young myself either... Even if I often like to see myself that way

                          I debated with myself about going entirely SMD. I eventually settled to go that way, because many components were going to be SMD anyway: the CPLD, the micro controller, USB connector and SD card socket. But to be honest, I wanted to go this way because I wanted to see if I could do it so this is my small mount everest to conquer. We will see how it pans out. The good news is that the boards turned out to be very affordable - the order went in yesterday. If it turns out to be difficult to construct, I can modify the design with through hole components for the parts where that option is available. I tried to align parts in a way where there would be some maneuvering space around them - towards the end of the layout I realized I had placed some parts too close to each other to facilitate hand assembly.

                          To continue on the SMD theme, I also want to say that I believe the board layout was easier to do this way. Currently the only through hole parts are the pin headers and the crystal. Going through hole with the other components would probably have required a larger board. I attached a printout of the top and bottom of the board (I eventually settled on Eagle, dare I say due to the fact it seemed to have more complete SMD part part libraries...). With the XC9572XL and its 100 pin package there is quite a bit of routing pressure to bring the signals out. Even though the board does not look like much, it took me probably 50 hours or so to manually place and route after the first version of the schematic was done. A lot of that was learning curve and early design changes, finding the appropriate packages, but also just getting the signals where they need to go. I think the next board will go very much faster.

                          Originally posted by Stuart View Post
                          I see the schematic PDF with lots of lovely interfaces on it. How does one access such a device? Is it all memory mapped ports, or ...?
                          Basically the idea is that all signals from the Mini Cortex CPUBUS go to the CPLD. There is a 11 bit parallel bus between the microcontroller and the CPLD. In addition the SPI bus of the SD card goes to both the micro and the CPLD. With that, the actual interface topology will be up to the CPLD configuration.

                          You are right, my idea is that the ports will be memory mapped and actually on the mini cortex that is the only option as the CRU bus does not arrive at the CF connector. This also matches the FPGA design I did on the breadboard - the SD card interface is memory mapped.

                          There are 8 memory locations that are available. The existing SPI design requires two (one for SPI data read/write, one 1 bit register for SPI chip select and status read). I am planning that on some of the remaining memory locations there would be access to the extension connectors of the CPLD (12 signals - more would exist but I wanted to get the board done and did not want reposition the parts yet again to route more signals out). A couple of registers would be a mailbox interface between the micro and TMS9995. That mailbox would be the means of interprocessor communication, providing access to the vast array of peripherals available on the micro. Of particular interest there are the serial port and the USB port. I also brought out the I2C bus of the micro to some header pins.

                          The NXP LPC1343 microcontroller is tiny in size but has an impressive amount of stuff in it. It has a 32-bit ARM Cortex M3 processor core running at up 72MHz, 32K of flash ROM and 8K of RAM. It has a very handy boot loader feature, basically you short one pin to ground and it's built in boot ROM makes the chip look like a 32K FAT12 USB memory device, allowing one to drag and drop in a 32K firmware image. I haven't tried that yet, in my test setup I have used a raspberry pi connected to the serial port of the micro and I've used the serial boot loader feature of the chip. In case one wants to use more of the micro controllers features on this board, one can just route the 11 bit bus going to the CPLD thought the CPLD to its extension connectors. I tried to keep things flexible there.

                          I also wanted to go with these particular chips and packages (XC9572XL and LPC1343) because for both there is a pin compatible upgrade path (XC95144XL with 144 macrocells, and LPC1347 with 64K Flash).

                          Erik
                          Attached Files

                          Comment


                            Ok so I posted a few years ago that I have a cortex and was going to have a go at getting it going.....then life took over.

                            So anyway now I really am about to try and resurrect it.

                            I have the original mk1 Cortex but with the Yamaha display and the wd floppy controller both on sub pcb's on flying leads, I also did the 256k memory mod.

                            Have got all the boards on a bench and if interest is there I will post some pictures as I go.

                            My plan is as follows over the next 8-10 weeks.

                            1) to allow me to use a TFT screen--order a video console to VGA converter from ebay (done)
                            2) spray clean with PCB cleaner all the boards as very grubby with 25+ yrs of loft grime accumulated( bits bought and next to be done)
                            3) change electrolytic's on PSU but may also get a Switch Miode PSU to replace original unit
                            4) change electrolytic's on all other PCB'S and the tantalum caps from the main board.
                            5) remove all 74xx logic chips, test and replace one by one.
                            6) remove all components from tape unit, old video rams, old TV display from motherboard.
                            6) remake all flying leads to suit a new layout with the sub boards being on a Perspex plate mounted above main board.
                            7) power up from bench supply at low voltage then fit main PSU.
                            prey that the 25 year old Cdos2.0 disk still works !
                            9) fit it back into original case.

                            then I am thinking of making a new pcb sub board to use include 512k of static ram.

                            only for fun and to see if I can get it going.

                            Comment


                              Yes please to some pictures, and progress reports as time allows.

                              You're in the UK somewhere?

                              Comment


                                yes Essex in UK

                                Comment

                                Working...
                                X