• Forth processor project1 Re: Is it time for another Forth chip?

    From Wayne morellini@21:1/5 to Wayne morellini on Sat Sep 3 21:59:30 2022
    On Tuesday, June 7, 2022 at 7:52:48 PM UTC+10, Wayne morellini wrote:
    I know we are waiting to hear what the 6Ghz chip Stephen has been working with will turn out like, and what Green Arrays will release for the glasses (which type of thing demands an advanced design). But recently, I saw a document on Colorforth for ARM,
    and comparisons to Swift Forth etc. Which got me wondering about a lower end design. Now, with the passing of Doctor Ting, it reminds me of the Mup21 he had that kicked things off, and Jeff's work latter. Isn't it time we had something more like these
    designs upgraded? 16 bit or more versions?

    Syncing forth processor project threads.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wayne morellini@21:1/5 to Wayne morellini on Sun Sep 4 08:26:11 2022
    On Sunday, September 4, 2022 at 2:59:31 PM UTC+10, Wayne morellini wrote:
    On Tuesday, June 7, 2022 at 7:52:48 PM UTC+10, Wayne morellini wrote:
    I know we are waiting to hear what the 6Ghz chip Stephen has been working with will turn out like, and what Green Arrays will release for the glasses (which type of thing demands an advanced design). But recently, I saw a document on Colorforth for
    ARM, and comparisons to Swift Forth etc. Which got me wondering about a lower end design. Now, with the passing of Doctor Ting, it reminds me of the Mup21 he had that kicked things off, and Jeff's work latter. Isn't it time we had something more like
    these designs upgraded? 16 bit or more versions?
    Syncing forth processor project threads.

    Forth processor project

    Is it time for another Forth chip?

    https://groups.google.com/u/2/g/comp.lang.forth/c/6adve-Z1ppU

    Designing a Forth Processor?

    https://groups.google.com/u/2/g/comp.lang.forth/c/9lpG9yey_NQ

    A low cost chip prototyping technique.

    https://groups.google.com/u/2/g/comp.lang.forth/c/s27tSebmF-I

    Comments: ColorForth binary in JavaScript!

    https://groups.google.com/u/2/g/comp.lang.forth/c/3py7TwKu6b0

    Looking for some advice on Offete p8, p16, p24, p32, p64. Ep16, ep24, ep32, and others.

    https://groups.google.com/u/2/g/comp.lang.forth/c/EMgCYdV8NR8

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Tse@21:1/5 to Wayne morellini on Sun Feb 26 16:13:51 2023
    On Sunday, September 4, 2022 at 11:26:12 PM UTC+8, Wayne morellini wrote:
    On Sunday, September 4, 2022 at 2:59:31 PM UTC+10, Wayne morellini wrote:
    On Tuesday, June 7, 2022 at 7:52:48 PM UTC+10, Wayne morellini wrote:
    I know we are waiting to hear what the 6Ghz chip Stephen has been working with will turn out like, and what Green Arrays will release for the glasses (which type of thing demands an advanced design). But recently, I saw a document on Colorforth for
    ARM, and comparisons to Swift Forth etc. Which got me wondering about a lower end design. Now, with the passing of Doctor Ting, it reminds me of the Mup21 he had that kicked things off, and Jeff's work latter. Isn't it time we had something more like
    these designs upgraded? 16 bit or more versions?
    Syncing forth processor project threads.
    Forth processor project

    Is it time for another Forth chip?

    https://groups.google.com/u/2/g/comp.lang.forth/c/6adve-Z1ppU

    Designing a Forth Processor?

    https://groups.google.com/u/2/g/comp.lang.forth/c/9lpG9yey_NQ

    A low cost chip prototyping technique.

    https://groups.google.com/u/2/g/comp.lang.forth/c/s27tSebmF-I

    Comments: ColorForth binary in JavaScript!

    https://groups.google.com/u/2/g/comp.lang.forth/c/3py7TwKu6b0

    Looking for some advice on Offete p8, p16, p24, p32, p64. Ep16, ep24, ep32, and others.

    https://groups.google.com/u/2/g/comp.lang.forth/c/EMgCYdV8NR8

    after all that has been said, ultimately, what matters is 1) low power 2) high performance 3) easy to program 4) tools available 5) cheap. so if a 8bit cpu can do the job, why use 32bit, green array's version may be the best candidate to upset the status
    quo, especially if it has the ability to emulate any IO and still have all the atributes above, BUT it also must be able to access large memories or else it will not be able to do memory intensive product. still, as a super duper IO controller, it can
    have mass market appeal especially in china for product manufacturing. if i am green array, now is a good time to go to china, especially when it is literally cowboy season where too much funds chasing all kinds of silicon solution ideas. if no one in
    the world is willing to fund " dead end " chips, green Array got nothing to lose and everything to gain. if this even works 50%, at least forthers may still have our day in the sun. imagine a green array chip in every product shipped to the rest of the
    world, much bigger market than the us.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lorem Ipsum@21:1/5 to John Tse on Sun Feb 26 17:03:25 2023
    On Sunday, February 26, 2023 at 8:13:53 PM UTC-4, John Tse wrote:
    On Sunday, September 4, 2022 at 11:26:12 PM UTC+8, Wayne morellini wrote:
    On Sunday, September 4, 2022 at 2:59:31 PM UTC+10, Wayne morellini wrote:
    On Tuesday, June 7, 2022 at 7:52:48 PM UTC+10, Wayne morellini wrote:
    I know we are waiting to hear what the 6Ghz chip Stephen has been working with will turn out like, and what Green Arrays will release for the glasses (which type of thing demands an advanced design). But recently, I saw a document on Colorforth
    for ARM, and comparisons to Swift Forth etc. Which got me wondering about a lower end design. Now, with the passing of Doctor Ting, it reminds me of the Mup21 he had that kicked things off, and Jeff's work latter. Isn't it time we had something more like
    these designs upgraded? 16 bit or more versions?
    Syncing forth processor project threads.
    Forth processor project

    Is it time for another Forth chip?

    https://groups.google.com/u/2/g/comp.lang.forth/c/6adve-Z1ppU

    Designing a Forth Processor?

    https://groups.google.com/u/2/g/comp.lang.forth/c/9lpG9yey_NQ

    A low cost chip prototyping technique.

    https://groups.google.com/u/2/g/comp.lang.forth/c/s27tSebmF-I

    Comments: ColorForth binary in JavaScript!

    https://groups.google.com/u/2/g/comp.lang.forth/c/3py7TwKu6b0

    Looking for some advice on Offete p8, p16, p24, p32, p64. Ep16, ep24, ep32, and others.

    https://groups.google.com/u/2/g/comp.lang.forth/c/EMgCYdV8NR8
    after all that has been said, ultimately, what matters is 1) low power 2) high performance 3) easy to program 4) tools available 5) cheap. so if a 8bit cpu can do the job, why use 32bit, green array's version may be the best candidate to upset the
    status quo, especially if it has the ability to emulate any IO and still have all the atributes above, BUT it also must be able to access large memories or else it will not be able to do memory intensive product. still, as a super duper IO controller, it
    can have mass market appeal especially in china for product manufacturing. if i am green array, now is a good time to go to china, especially when it is literally cowboy season where too much funds chasing all kinds of silicon solution ideas. if no one
    in the world is willing to fund " dead end " chips, green Array got nothing to lose and everything to gain. if this even works 50%, at least forthers may still have our day in the sun. imagine a green array chip in every product shipped to the rest of
    the world, much bigger market than the us.

    The Green Array GA144 has been available for what, a decade? Yet, there's no evidence of it finding it's way into any serious products. They originally bought some thousands of chips, because that was the minimum run for sampling purposes! There's no
    indication they ever went back for a second run of parts.

    There is no "day in the sun" for Forth. It had it's shining moment when it appeared on the cover of Byte magazine. It's been a gradual downgrade ever since. I understand it no longer appears on a ranking of the top computer programming languages (by "
    top", I mean one in a hundred programmers have heard of it).

    Forth is what it is. Use it, like it, don't use it, don''t like it. The world does not care. But there is virtually nothing to gain by anyone to produce a CPU chip that is in some way, optimized for running Forth. Even if it runs Forth twice as fast,
    you can get that every easily from the pool of thousands of CPU chips now on the market.

    To conceive, design and introduce a new product, you should first ask, "What problem am I trying to solve"? I think you will find there are no more problems in the CPU world other than the tradeoffs of power, performance and cost. I see no reason to
    think a Forth oriented CPU design would be any better at this than what's available today.

    --

    Rick C.

    ---++ Get 1,000 miles of free Supercharging
    ---++ Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From none) (albert@21:1/5 to gnuarm.deletethisbit@gmail.com on Mon Feb 27 13:31:44 2023
    In article <270b46a1-fb7d-420c-86fa-d37a90295c60n@googlegroups.com>,
    Lorem Ipsum <gnuarm.deletethisbit@gmail.com> wrote:
    <SNIP>
    To conceive, design and introduce a new product, you should first ask,
    "What problem am I trying to solve"? I think you will find there are no
    more problems in the CPU world other than the tradeoffs of power,
    performance and cost. I see no reason to think a Forth oriented CPU
    design would be any better at this than what's available today.

    +1

    Rick C.
    --
    Don't praise the day before the evening. One swallow doesn't make spring.
    You must not say "hey" before you have crossed the bridge. Don't sell the
    hide of the bear until you shot it. Better one bird in the hand than ten in
    the air. First gain is a cat spinning. - the Wise from Antrim -

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marcel Hendrix@21:1/5 to none albert on Mon Feb 27 12:46:40 2023
    On Monday, February 27, 2023 at 1:31:47 PM UTC+1, none albert wrote:
    In article <270b46a1-fb7d-420c...@googlegroups.com>,
    Lorem Ipsum <gnuarm.del...@gmail.com> wrote:
    <SNIP>
    To conceive, design and introduce a new product, you should first ask, >"What problem am I trying to solve"? I think you will find there are no >more problems in the CPU world other than the tradeoffs of power, >performance and cost. I see no reason to think a Forth oriented CPU
    design would be any better at this than what's available today.
    +1

    That invites a contrary opinion :--)

    From personal experience, development of switch-mode power supplies
    involves a joint effort of a group of highly specialized engineers. Developing prototype is hell, because a tiny error in a board layout, the software, or in doing measurements for debugging, can lead to catastrophic failure with
    no option for repair. For some reason they always use the latest chips (not
    all bugs known), and for some reason the manuals become bigger and
    bigger (1000 pages for a digital controller with programmable I/O?). The
    result is that for some types of bug, only a single person knows enough
    to work on it, and nobody is able to help him because they have not read
    the 1000 pages yet.

    It would certainly help to have chips with an on-board RTOS and open
    source drivers for all on-board I/O, plus ways to easily configure and
    test stuff interactively.

    The idea would be to make development less dependent on one or two
    software engineers that know everything, and make it possible for
    hardware people to at least intelligently step in for testing and
    debugging.

    -marcel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lorem Ipsum@21:1/5 to Marcel Hendrix on Tue Feb 28 21:20:31 2023
    On Monday, February 27, 2023 at 4:46:42 PM UTC-4, Marcel Hendrix wrote:
    On Monday, February 27, 2023 at 1:31:47 PM UTC+1, none albert wrote:
    In article <270b46a1-fb7d-420c...@googlegroups.com>,
    Lorem Ipsum <gnuarm.del...@gmail.com> wrote:
    <SNIP>
    To conceive, design and introduce a new product, you should first ask, >"What problem am I trying to solve"? I think you will find there are no >more problems in the CPU world other than the tradeoffs of power, >performance and cost. I see no reason to think a Forth oriented CPU >design would be any better at this than what's available today.
    +1
    That invites a contrary opinion :--)

    From personal experience, development of switch-mode power supplies
    involves a joint effort of a group of highly specialized engineers. Developing
    prototype is hell, because a tiny error in a board layout, the software, or in
    doing measurements for debugging, can lead to catastrophic failure with
    no option for repair. For some reason they always use the latest chips (not all bugs known), and for some reason the manuals become bigger and
    bigger (1000 pages for a digital controller with programmable I/O?). The result is that for some types of bug, only a single person knows enough
    to work on it, and nobody is able to help him because they have not read
    the 1000 pages yet.

    It would certainly help to have chips with an on-board RTOS and open
    source drivers for all on-board I/O, plus ways to easily configure and
    test stuff interactively.

    The idea would be to make development less dependent on one or two
    software engineers that know everything, and make it possible for
    hardware people to at least intelligently step in for testing and
    debugging.

    I'm sure you think you have made a convincing argument, but of what exactly? Some MCU devices or worse, larger chips like they use in rPi and cell phone devices, have large complex manuals. That's because there are many systems on those devices, each
    of which take many pages to document. But they still make 8051 devices, and other MCUs that are very basic and have much less documentation.

    So, what exactly is your point? You don't even mention stacks or Forth support.

    BTW, I just had some strawberries that looked fantastic, right red, nice size. But they were a disappointment, in that they were only a bit sweet, and much of the berry (the bits you can't see under the leaves and inside) were white and almost woody.
    At least I got my roughage today.

    See, that was not terribly relevant to the topic either.

    --

    Rick C.

    --+-- Get 1,000 miles of free Supercharging
    --+-- Tesla referral code - https://ts.la/richard11209

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)