I'd expect everything to stay the same; only we'll be able to use INB, OUTB, & DIRB.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cheers,
Simon
www.norfolkhelicopterclub.co.uk
You'll always have as many take-offs as landings, the trick is to be sure you can take-off again ;-) BTW: I type as I'm thinking, so please don't take any offense at my writing style
The interpreter and bytecode seems almost certain to be the same for the 64-pin Prop I but will have to change for Prop II because 16-bit words are currently used as address pointers in the Object Method Tables and as return addresses on the stack, for 256KB addressing they will need to be 18-bit. Conveniently though, with everything aligned on long boundaries, the 18-bits can be right-shifted to fit 16-bits and back again with no errors introduced.
Ken Peterson said...
IC design is one thing I've never done. Good luck with that. Is there any speculation yet about a launch date for either chip?
wrt Prop-2, it's too early to have any projection other than the·vague timeframe given already. Prop-1B we can't speculate either because there is a roadblock preventing progress.
Not really.· The memory locations for INB / OUTB / DIRB are there, but none of the special hardware exists.· Try setting DIRB and OUTB, then see if you can read it from another cog using INB.· You'll find that it doesn't work. ·
It's not the design its the design tools, in order to verify that the schematic matches the layout you have to run a utility called LVS (Layout verses Schematic). Without this tool we cannot not justify paying many thousands of dollars to fabricate the chip because we have no indication of the "correctness" of the design wrt to the schematic. This tool when run on the design crashes the computer, and until this issue is resolved we cannot verify the design and it will sit on the shelf until we can get it to verify. And before we start getting "are we there yet" posts, we have been in this spot for many months now, and likely will for a while longer.
Ken Peterson, · I'm going to lean toward human error... the LVS tool is fine, granted it has limitations, but they are the sort of limitations that I have seen across the board with other LVS tools.· If you know and understand the various quirks about the tool and what it's trying to tell you then most if not all f your problems will go away.· Nothing is waived; all layouts must pass with 100% schematic correspondence.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Beau Schwabe
IC Layout Engineer
Parallax, Inc.
I've never done chip design before and this is all very interesting. I'm sure there are other forum readers who are also interested in learning more about the process.
From what I understand (I haven't used a professional IC layout program since Cadence in college) it requires some massaging to get it to work correctly. What I recollect from a conversation with Beau, it takes fiddling with some script files to get things in a shape the LVS likes to see them, but that the required changes aren't always obvious (iow it can be a bit of black art).
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cheers,
Simon
www.norfolkhelicopterclub.co.uk
You'll always have as many take-offs as landings, the trick is to be sure you can take-off again ;-)
BTW: I type as I'm thinking, so please don't take any offense at my writing style
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Paul Baker
Propeller Applications Engineer
Parallax, Inc.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Paul Baker
Propeller Applications Engineer
Parallax, Inc.
Post Edited (Paul Baker (Parallax)) : 4/22/2008 11:13:33 PM GMT
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
I'm going to lean toward human error... the LVS tool is fine, granted it has limitations, but they are the sort of limitations that I have seen across the board with other LVS tools.· If you know and understand the various quirks about the tool and what it's trying to tell you then most if not all f your problems will go away.· Nothing is waived; all layouts must pass with 100% schematic correspondence.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Beau Schwabe
IC Layout Engineer
Parallax, Inc.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Paul Baker
Propeller Applications Engineer
Parallax, Inc.
Post Edited (Paul Baker (Parallax)) : 4/23/2008 6:19:31 PM GMT