It would port over to any machine that implemented some kind of NVRAM and exposed it as a nonvolatile.library... which i think would be the best way to do nvram on any machine..
But yes. No other machine has that yet.
Clock generator for TF360 rev 1
Moderators: terriblefire, Terriblefire Moderator
-
- Moderator Team
- Posts: 5387
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Clock generator for TF360 rev 1
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: Clock generator for TF360 rev 1
Software controlled clock sounds great. To prevent runaway code looping all memory and setting unexpected frequencies, two registers could be used in sequence, or being able to optionally lock further settings until reset would also prevent (to a degree) any rogue program from misbehaving.
Having said that, would it still be worth to leave PCB space for a couple of GPIOs exposed from CPLD (can CPLD pins be configured with pullups/pulldowns) for future use? Could be used to disable the 64k autoconfig device, force 50MHz for non-boots, disable on-board IDE etc.
Having said that, would it still be worth to leave PCB space for a couple of GPIOs exposed from CPLD (can CPLD pins be configured with pullups/pulldowns) for future use? Could be used to disable the 64k autoconfig device, force 50MHz for non-boots, disable on-board IDE etc.
-
- Moderator Team
- Posts: 5387
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Clock generator for TF360 rev 1
Possibly. Although im not letting this get set raw. Its an allowed list of frequencies selected from a table.richx wrote: ↑Sat Sep 14, 2019 4:56 pm Software controlled clock sounds great. To prevent runaway code looping all memory and setting unexpected frequencies, two registers could be used in sequence, or being able to optionally lock further settings until reset would also prevent (to a degree) any rogue program from misbehaving.
Nah... there arent any free pins. All 288 pins are in used on this board. i've had to be cruel and creative to get this to fit as it is.Having said that, would it still be worth to leave PCB space for a couple of GPIOs exposed from CPLD (can CPLD pins be configured with pullups/pulldowns) for future use? Could be used to disable the 64k autoconfig device, force 50MHz for non-boots, disable on-board IDE etc.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
-
- Moderator Team
- Posts: 5387
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Clock generator for TF360 rev 1
OK so the rev 1 is done and i've chosen this chip for the clockgen...
https://uk.rs-online.com/web/p/pll-freq ... s/1628970/
Reasons are that its relatively simple, small footprint and cheap ish. It gives good multilpy options in the range we want.
The firmware will not let you hit these pins directly they'll be chosen from a table. The onboard crystal will be a the same SMD form factor crystal but at 25Mhz.
The output frequencies you can select will be
I'll also allow a straight 14Mhz option.
There is a jumper to disable the 060 and onboards.
I've dramatically beefed up the decoupling in critical areas. Not sure how much this is needed but it wont hurt.
I'm going to recommend a -7 RAMCPLD if you want to get to 100Mhz. I think we're basically hitting the CPLD limits now.
https://uk.rs-online.com/web/p/pll-freq ... s/1628970/
Reasons are that its relatively simple, small footprint and cheap ish. It gives good multilpy options in the range we want.
The firmware will not let you hit these pins directly they'll be chosen from a table. The onboard crystal will be a the same SMD form factor crystal but at 25Mhz.
The output frequencies you can select will be
Multiplier | RAMCLK | CPUCLK |
3.75 | 93.75 | 46.875 |
4 | 100 | 50 |
5 | 125 | 62.5 |
6 | 150 | 75 |
6.25 | 156.25 | 78.125 |
6.333 | 158.325 | 79.1625 |
8 | 200 | 100 |
8.3333 | 208.3325 | 104.16625 |
There is a jumper to disable the 060 and onboards.
I've dramatically beefed up the decoupling in critical areas. Not sure how much this is needed but it wont hurt.
I'm going to recommend a -7 RAMCPLD if you want to get to 100Mhz. I think we're basically hitting the CPLD limits now.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."