Re: [M100] REXCPM Stalled @ Loading/Activating TS-Dos

2020-07-26 Thread Greg Swallow


If I Power Cycle after the "hang" the M100 is at Cold Start (1/1/2000)


On 7/26/20 9:30 PM, Greg Swallow wrote:


Starting with a fresh (cold start) M100:

1.    Set DATE$, DAY$, and TIME$

2.    Using terminal program (moserial) to drop RXCINI.DO to M100

3.    Disconnect MoSerial and start LaddieAlpha

4.    From BASIC:
       RUN"RXCINI.DO

5.    Load REX Code:    YES
       Init REX Dir:            YES

        
        ... (y/n)? Y

6.    REXCPM INITIALIZE V1

     Loading at 62000 <... ...> 62879

            Action=19200, Load, Init
            Format:  XX
            Name:    RXC_11

7.    28672 Format:  XX
                    Name:    RXC_11
                    Initializing Directory ...
                    Complete!!

        Ok

8.    Cycle Power

9.    From BASIC:
        CALL 63012

10.  From MENU:
        RXCMGR

11.   RXCMGR 1.0 GroupROM free: 16

     Load:

12.   Loading from image file name:TSD100

13.    Cycle Power

14.    RXCMGR 1.0 GroupROM   free: 15

            TSD100        ---

15.    Highlight TSD100 and press ENTER

16.    Install ROM (Y/N)? Y

And she sits there

GregS <><

On 7/26/20 8:03 PM, Stephen Adolph wrote:
Not sure actually.  I dont recall what error that is.  Is this a rex 
error?


When you say you are trying to load it, exactly what are you doing?

And what are you doing to get the error?

Thx


On Sunday, July 26, 2020, Greg Swallow > wrote:


Jim/Steve,

Got RXCMGR loaded and running. Used it to load TSD100 and SUP10,
but both gave a "model mismatch" error when tryied to
start/activate. Several reset/cold starts/re do and now stalls
when try to activate TSD100. Have let M100 sit w/ no power,
including memory, to be sure REXCPM is in "default state."

Only thing I can think of is the system ROM is a modified M102
Y2K chip. Also changed Microsoft (c) banner to serial number.

Any idea?

GregS <><



Re: [M100] REXCPM Stalled @ Loading/Activating TS-Dos

2020-07-26 Thread Greg Swallow

Starting with a fresh (cold start) M100:

1.    Set DATE$, DAY$, and TIME$

2.    Using terminal program (moserial) to drop RXCINI.DO to M100

3.    Disconnect MoSerial and start LaddieAlpha

4.    From BASIC:
       RUN"RXCINI.DO

5.    Load REX Code:    YES
       Init REX Dir:            YES

        
        ... (y/n)? Y

6.    REXCPM INITIALIZE V1

     Loading at 62000 <... ...> 62879

            Action=19200, Load, Init
            Format:  XX
            Name:    RXC_11

7.    28672 Format:  XX
                    Name:    RXC_11
                    Initializing Directory ...
                    Complete!!

        Ok

8.    Cycle Power

9.    From BASIC:
        CALL 63012

10.  From MENU:
        RXCMGR

11.   RXCMGR 1.0 GroupROM free: 16

     Load:

12.   Loading from image file name:TSD100

13.    Cycle Power

14.    RXCMGR 1.0 GroupROM   free: 15

            TSD100        ---

15.    Highlight TSD100 and press ENTER

16.    Install ROM (Y/N)? Y

And she sits there

GregS <><

On 7/26/20 8:03 PM, Stephen Adolph wrote:
Not sure actually.  I dont recall what error that is.  Is this a rex 
error?


When you say you are trying to load it, exactly what are you doing?

And what are you doing to get the error?

Thx


On Sunday, July 26, 2020, Greg Swallow > wrote:


Jim/Steve,

Got RXCMGR loaded and running. Used it to load TSD100 and SUP10,
but both gave a "model mismatch" error when tryied to
start/activate. Several reset/cold starts/re do and now stalls
when try to activate TSD100. Have let M100 sit w/ no power,
including memory, to be sure REXCPM is in "default state."

Only thing I can think of is the system ROM is a modified M102 Y2K
chip. Also changed Microsoft (c) banner to serial number.

Any idea?

GregS <><



Re: [M100] REXCPM Stalled @ Loading/Activating TS-Dos

2020-07-26 Thread Stephen Adolph
Not sure actually.  I dont recall what error that is.  Is this a rex error?

When you say you are trying to load it, exactly what are you doing?

And what are you doing to get the error?

Thx


On Sunday, July 26, 2020, Greg Swallow  wrote:

> Jim/Steve,
>
> Got RXCMGR loaded and running. Used it to load TSD100 and SUP10, but both
> gave a "model mismatch" error when tryied to start/activate. Several
> reset/cold starts/re do and now stalls when try to activate TSD100. Have
> let M100 sit w/ no power, including memory, to be sure REXCPM is in
> "default state."
>
> Only thing I can think of is the system ROM is a modified M102 Y2K chip.
> Also changed Microsoft (c) banner to serial number.
>
> Any idea?
>
> GregS <><
>
>


Re: [M100] REXCPM Stalled @ Loading/Activating TS-Dos

2020-07-26 Thread Stephen Adolph
Loading to ram not optrom.


On Sunday, July 26, 2020, Greg Swallow  wrote:

> Jim/Steve,
>
> Got RXCMGR loaded and running. Used it to load TSD100 and SUP10, but both
> gave a "model mismatch" error when tryied to start/activate. Several
> reset/cold starts/re do and now stalls when try to activate TSD100. Have
> let M100 sit w/ no power, including memory, to be sure REXCPM is in
> "default state."
>
> Only thing I can think of is the system ROM is a modified M102 Y2K chip.
> Also changed Microsoft (c) banner to serial number.
>
> Any idea?
>
> GregS <><
>
>


Re: [M100] REXCPM Stalled @ Loading/Activating TS-Dos

2020-07-26 Thread Greg Swallow
Jim/Steve,

Got RXCMGR loaded and running. Used it to load TSD100 and SUP10, but both gave 
a "model mismatch" error when tryied to start/activate. Several reset/cold 
starts/re do and now stalls when try to activate TSD100. Have let M100 sit w/ 
no power, including memory, to be sure REXCPM is in "default state."

Only thing I can think of is the system ROM is a modified M102 Y2K chip. Also 
changed Microsoft (c) banner to serial number.

Any idea?

GregS <><



[M100] Keyboard ribbon cable replacement for a Model 102

2020-07-26 Thread kjohnson3 . 14
Good Evening Folks,

I received my REXCPM from Steve, so I had to pull apart one of my Model 102.

I noticed the keyboard ribbon cable was damaged, either by myself or time.
I had problems with this unit and the keyboard, I assumed the keys needed
cleaning.

Does anyone have a source for these cables? I took some measurements and
looked on Mouser, but I couldn't find anything modern that would fit.

I figured someone out there must have had this problem as well.

Thank you,
Keith


Re: [M100] LCD Botton 4 Lines (WAS) Listserv Search

2020-07-26 Thread Chris Fezzler
 Everything has a purpose, I guess.  I learned to read a schematic better.  I 
learned how to use a logic probe and my mutli-meter better.  I got experience 
de-soldering.  I replaced the internal battery.  So if it holds, I'll have a 
sweet Model T with REXCPM installed.  
On Sunday, July 26, 2020, 06:26:04 PM EDT, Jeffrey Birt 
 wrote:  
 
 
Excellent! Let us know!

  

Jeff Birt

  

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 5:19 PM
To: m...@bitchin100.com
Subject: Re: [M100] LCD Botton 4 Lines (WAS) Listserv Search

  

Working but "uncle" LOL.

  

After logic prob test, I got some pliers and gently squeezed the LCD connector 
to ensure good contact with the clip and wires before reinstalling.

  

Fired it up.  Nothing.  Blank screen.  Warm boot, nothing.  Hard rest, LCD 
pixels went dark momentarily.  Then nothing.

  

About to call it quits but something told me to switch off, hold just CTRL and 
BREAK while turning on (no reset button).

  

It fired up perfect, all lines.  

  

Who knows?

  

We'll see if it sticks before installing REXCPM.

  

  

  

On Sunday, July 26, 2020, 05:42:36 PM EDT, Chris Fezzler  
wrote: 

  

  

For what it is worth, logic probe results for LCD connector chip select pins:

  

CS01 (pin 18) = H

CS20 (pin 14) = H

CS21 (pin 12) = H

CS22 (pin 10) = H

CS23 (pin   8) = H

CS24 (pin   7) = H

CS25 (pin 16) = L

CS26 (pin 15) = L

CS27 (pin 13) = L

CS28 (pin 11) = L

CS29 (pin   9) = L

 

I took the prob positive from C83 and ground from C8.

  

  

On Sunday, July 26, 2020, 03:55:00 PM EDT, Chris Fezzler  
wrote: 

  

  

No after market ROM.

  

Logically, I would think the fact that the top four lines are perfect, the hard 
reset produces a perfect Menu screen, and just the bottom four lines are 
garbled would be a clue where to look.

  

I know nothing other than reading a lot off Internet.  My instinct tells me the 
issue is a component that regulates power or signals to the LCD driver chips 
for the bottom half of the screen.  The are getting power (because we see 
gibberish and the perfect Menu screen) but perhaps it is the wrong voltage or 
intermittent power or signal.

  

Thoughts are:

  

Capacitors C47 or C54 and or M17 and/or M25.

  

But I don't know how to determine their impact on the issue.

 

  

  

  

On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt  
wrote: 

  

  

When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.

 

If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.

 

Do you have any sort of aftermarket ROM installed? 

 

Very interesting problem. 

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 9:47 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

Gladly.

 

 

 

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt  
wrote: 

 

 

Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) to test chip select lines on the 
LCD connector (Pins 14, 12, 10, 8, 7, 16,15,13,11, 9, and CS1=Pin? - schematics 
blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
 wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and 

Re: [M100] LCD Botton 4 Lines (WAS) Listserv Search

2020-07-26 Thread Jeffrey Birt
Excellent! Let us know!

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 5:19 PM
To: m...@bitchin100.com
Subject: Re: [M100] LCD Botton 4 Lines (WAS) Listserv Search

 

Working but "uncle" LOL.

 

After logic prob test, I got some pliers and gently squeezed the LCD connector 
to ensure good contact with the clip and wires before reinstalling.

 

Fired it up.  Nothing.  Blank screen.  Warm boot, nothing.  Hard rest, LCD 
pixels went dark momentarily.  Then nothing.

 

About to call it quits but something told me to switch off, hold just CTRL and 
BREAK while turning on (no reset button).

 

It fired up perfect, all lines.  

 

Who knows?

 

We'll see if it sticks before installing REXCPM.

 

 

 

On Sunday, July 26, 2020, 05:42:36 PM EDT, Chris Fezzler mailto:fezz...@yahoo.com> > wrote: 

 

 

For what it is worth, logic probe results for LCD connector chip select pins:

 

CS01 (pin 18) = H

CS20 (pin 14) = H

CS21 (pin 12) = H

CS22 (pin 10) = H

CS23 (pin   8) = H

CS24 (pin   7) = H

CS25 (pin 16) = L

CS26 (pin 15) = L

CS27 (pin 13) = L

CS28 (pin 11) = L

CS29 (pin   9) = L

 

I took the prob positive from C83 and ground from C8.

 

 

On Sunday, July 26, 2020, 03:55:00 PM EDT, Chris Fezzler mailto:fezz...@yahoo.com> > wrote: 

 

 

No after market ROM.

 

Logically, I would think the fact that the top four lines are perfect, the hard 
reset produces a perfect Menu screen, and just the bottom four lines are 
garbled would be a clue where to look.

 

I know nothing other than reading a lot off Internet.  My instinct tells me the 
issue is a component that regulates power or signals to the LCD driver chips 
for the bottom half of the screen.  The are getting power (because we see 
gibberish and the perfect Menu screen) but perhaps it is the wrong voltage or 
intermittent power or signal.

 

Thoughts are:

 

Capacitors C47 or C54 and or M17 and/or M25.

 

But I don't know how to determine their impact on the issue.

 

 

 

 

On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt mailto:bir...@soigeneris.com> > wrote: 

 

 

When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.

 

If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.

 

Do you have any sort of aftermarket ROM installed? 

 

Very interesting problem. 

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 9:47 AM
To: m...@bitchin100.com  
Subject: Re: [M100] Listserv Search

 

Gladly.

 

 

 

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt mailto:bir...@soigeneris.com> > wrote: 

 

 

Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com  
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) 

  to test chip select lines on the LCD connector (Pins 14, 12, 10, 8, 7, 
16,15,13,11, 9, and CS1=Pin? - schematics blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
mailto:bir...@soigeneris.com> > wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and 

Re: [M100] LCD Botton 4 Lines (WAS) Listserv Search

2020-07-26 Thread Chris Fezzler
 Working but "uncle" LOL.
After logic prob test, I got some pliers and gently squeezed the LCD connector 
to ensure good contact with the clip and wires before reinstalling.
Fired it up.  Nothing.  Blank screen.  Warm boot, nothing.  Hard rest, LCD 
pixels went dark momentarily.  Then nothing.
About to call it quits but something told me to switch off, hold just CTRL and 
BREAK while turning on (no reset button).
It fired up perfect, all lines.  
Who knows?
We'll see if it sticks before installing REXCPM.


On Sunday, July 26, 2020, 05:42:36 PM EDT, Chris Fezzler 
 wrote:  
 
  For what it is worth, logic probe results for LCD connector chip select pins:
CS01 (pin 18) = HCS20 (pin 14) = HCS21 (pin 12) = HCS22 (pin 10) = HCS23 (pin   
8) = HCS24 (pin   7) = HCS25 (pin 16) = LCS26 (pin 15) = LCS27 (pin 13) = LCS28 
(pin 11) = LCS29 (pin   9) = L I took the prob positive from C83 and ground 
from C8.

On Sunday, July 26, 2020, 03:55:00 PM EDT, Chris Fezzler 
 wrote:  
 
  No after market ROM.
Logically, I would think the fact that the top four lines are perfect, the hard 
reset produces a perfect Menu screen, and just the bottom four lines are 
garbled would be a clue where to look.
I know nothing other than reading a lot off Internet.  My instinct tells me the 
issue is a component that regulates power or signals to the LCD driver chips 
for the bottom half of the screen.  The are getting power (because we see 
gibberish and the perfect Menu screen) but perhaps it is the wrong voltage or 
intermittent power or signal.
Thoughts are:
Capacitors C47 or C54 and or M17 and/or M25.
But I don't know how to determine their impact on the issue. 


On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt 
 wrote:  
 
 
When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.

  

If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.

  

Do you have any sort of aftermarket ROM installed? 

  

Very interesting problem. 

  

Jeff Birt

  

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 9:47 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

  

Gladly.

  

  

  

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt  
wrote: 

  

  

Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) to test chip select lines on the 
LCD connector (Pins 14, 12, 10, 8, 7, 16,15,13,11, 9, and CS1=Pin? - schematics 
blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
 wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).

 

Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.

 

Jeff BIrt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Wednesday, July 22, 2020 11:26 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

Here you go.  

 

 

 

On 

Re: [M100] Listserv Search

2020-07-26 Thread Chris Fezzler
 I typed same text in all lines.
Thanks.  Out beyond my skis here but learning and having some fun.  I'll 
probably fry the thing trying to fix it.
On Sunday, July 26, 2020, 05:05:36 PM EDT, Ken Pettit  
wrote:  
 
  Hey Chris,
 
 The LCD has 10 actual controller chips.  Each one controls 4 lines x 50 
pixels.  The two completely blank areas on the screen are the exact size of one 
of the controllers.  It looks like either those controllers are not 
functioning, or the enable signal driving them is not functioning (bad decoder 
IC, bad trace, bad connector).  I can't tell if the others have missing single 
pixel columns, or if the text is actually missing some letters (i.e. should 
line 6 actually say "test of the TRS-80" or does it really have spaces instead 
of text there?
 
 Ken
 
 On 7/26/20 12:54 PM, Chris Fezzler wrote:
  
  No after market ROM. 
  Logically, I would think the fact that the top four lines are perfect, the 
hard reset produces a perfect Menu screen, and just the bottom four lines are 
garbled would be a clue where to look. 
  I know nothing other than reading a lot off Internet.  My instinct tells me 
the issue is a component that regulates power or signals to the LCD driver 
chips for the bottom half of the screen.  The are getting power (because we see 
gibberish and the perfect Menu screen) but perhaps it is the wrong voltage or 
intermittent power or signal. 
  Thoughts are: 
  Capacitors C47 or C54 and or M17 and/or M25. 
  But I don't know how to determine their impact on the issue.   
  
  
  On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt 
 wrote:  
  
  
When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.
 
  
 
If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.
 
  
 
Do you have any sort of aftermarket ROM installed? 
 
  
 
Very interesting problem. 
 
  
 
Jeff Birt
 
  

From: M100  On Behalf Of Chris Fezzler
 Sent: Sunday, July 26, 2020 9:47 AM
 To: m...@bitchin100.com
 Subject: Re: [M100] Listserv Search
   
  
   
Gladly.
   
  
   
  
   
  
  
On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt  
wrote: 
   
  
   
  
  
Can you attach a picture of the cold boot screen too? 
 
 The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.
 
 
 
Jeff Birt
 
 

From: M100  On Behalf Of Chris Fezzler
 Sent: Saturday, July 25, 2020 6:20 PM
 To: m...@bitchin100.com
 Subject: Re: [M100] Listserv Search
   
 
 
ALERT: Beginner asking question.
   
 
 
Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)
   
 
   
(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 
   
 
  
So I purchased a logic prob (Elenco LP-900) to test chip select lines on the 
LCD connector (Pins 14, 12, 10, 8, 7, 16,15,13,11, 9, and CS1=Pin? - schematics 
blurry).
   
As I unboxed it I remembered I never used one before. :) 
   
 
   
- Where do I place the pos and neg alligator clips?
   
 
   
- Do I set the logic prob to 400PPS or 00.5PPS?
   
 
   
- In checking the chip select lines, am I looking for HI, LO, or PULSE?
   
 
   
I see no broken or corroded lines on the board.  
   
 
   
Thanks in advance.
   
 
   
 
   
 
   
 
   
 
   
 
   
 
   
 
   
 
 
On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
 wrote: 
   
 
   
 
  
This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).
 
 
 
Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.
 
 
 
Jeff BIrt
 
 

From: M100  On Behalf Of Chris Fezzler
 Sent: Wednesday, July 22, 2020 11:26 AM
 To: m...@bitchin100.com
 

Re: [M100] LCD Botton 4 Lines (WAS) Listserv Search

2020-07-26 Thread Chris Fezzler
 For what it is worth, logic probe results for LCD connector chip select pins:
CS01 (pin 18) = HCS20 (pin 14) = HCS21 (pin 12) = HCS22 (pin 10) = HCS23 (pin   
8) = HCS24 (pin   7) = HCS25 (pin 16) = LCS26 (pin 15) = LCS27 (pin 13) = LCS28 
(pin 11) = LCS29 (pin   9) = L I took the prob positive from C83 and ground 
from C8.

On Sunday, July 26, 2020, 03:55:00 PM EDT, Chris Fezzler 
 wrote:  
 
  No after market ROM.
Logically, I would think the fact that the top four lines are perfect, the hard 
reset produces a perfect Menu screen, and just the bottom four lines are 
garbled would be a clue where to look.
I know nothing other than reading a lot off Internet.  My instinct tells me the 
issue is a component that regulates power or signals to the LCD driver chips 
for the bottom half of the screen.  The are getting power (because we see 
gibberish and the perfect Menu screen) but perhaps it is the wrong voltage or 
intermittent power or signal.
Thoughts are:
Capacitors C47 or C54 and or M17 and/or M25.
But I don't know how to determine their impact on the issue. 


On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt 
 wrote:  
 
 
When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.

  

If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.

  

Do you have any sort of aftermarket ROM installed? 

  

Very interesting problem. 

  

Jeff Birt

  

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 9:47 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

  

Gladly.

  

  

  

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt  
wrote: 

  

  

Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) to test chip select lines on the 
LCD connector (Pins 14, 12, 10, 8, 7, 16,15,13,11, 9, and CS1=Pin? - schematics 
blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
 wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).

 

Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.

 

Jeff BIrt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Wednesday, July 22, 2020 11:26 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

Here you go.  

 

 

 

On Wednesday, July 22, 2020, 11:52:23 AM EDT, Stephen Adolph 
 wrote: 

 

 

a pic of the garbled screen would be great if you can do it.. thanks

 

On Wed, Jul 22, 2020 at 11:37 AM Chris Fezzler  wrote:


Sorry - typing too fast.  Top four lines of the screen.

 

Yes, mostly garbage all of the time.  Except a hard rest will generate a proper 
menu screen.

Yes, in BASIC the same.  But if I type in a test program and hit RUN the 
program will indeed run.

So the computer is getting the commands/keystrokes.  Just not displaying bottom 
four lines.

 

I think it is a component issue.

 

Re: [M100] Listserv Search

2020-07-26 Thread Ken Pettit

Hey Chris,

The LCD has 10 actual controller chips.  Each one controls 4 lines x 50 
pixels.  The two completely blank areas on the screen are the exact size 
of one of the controllers.  It looks like either those controllers are 
not functioning, or the enable signal driving them is not functioning 
(bad decoder IC, bad trace, bad connector).  I can't tell if the others 
have missing single pixel columns, or if the text is actually missing 
some letters (i.e. should line 6 actually say "test of the TRS-80" or 
does it really have spaces instead of text there?


Ken

On 7/26/20 12:54 PM, Chris Fezzler wrote:

No after market ROM.

Logically, I would think the fact that the top four lines are perfect, 
the hard reset produces a perfect Menu screen, and just the bottom 
four lines are garbled would be a clue where to look.


I know nothing other than reading a lot off Internet.  My instinct 
tells me the issue is a component that regulates power or signals to 
the LCD driver chips for the bottom half of the screen.  The are 
getting power (because we see gibberish and the perfect Menu screen) 
but perhaps it is the wrong voltage or intermittent power or signal.


Thoughts are:

Capacitors C47 or C54 and or M17 and/or M25.

But I don't know how to determine their impact on the issue.



On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt 
 wrote:



When comparing your two pictures, after rotating them right side up, I 
noticed just now that not only do you have blank blocks but some of 
the characters are reversed.  That is really bizarre. I’m not sure if 
that points to a problem with how the LCD drivers are being 
configured/initialized or what data is being sent to them.


If the driver ships are outputting a built-in font here it might be a 
chip configuration issue. If the display is always bit mapped, then it 
would be something else.


Do you have any sort of aftermarket ROM installed?

Very interesting problem.

Jeff Birt

*From:* M100  *On Behalf Of *Chris 
Fezzler

*Sent:* Sunday, July 26, 2020 9:47 AM
*To:* m...@bitchin100.com
*Subject:* Re: [M100] Listserv Search

Gladly.

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt 
mailto:bir...@soigeneris.com>> wrote:


Can you attach a picture of the cold boot screen too?

The positive and negative clips go to a +5 and ground source on the 
M100 PCB itself. The PPS setting if ‘Pulses Per Second’ when using it 
as a logic pulser, i.e. to inject a pulsing signal. On the chip select 
lines you should she them quickly toggling.


Jeff Birt

*From:*M100 > *On Behalf Of *Chris Fezzler

*Sent:* Saturday, July 25, 2020 6:20 PM
*To:* m...@bitchin100.com 
*Subject:* Re: [M100] Listserv Search

*ALERT*: Beginner asking question.

*Reminder:*Upon hard reset the LCD initializes perfectly and displays 
the main Menu screen perfectly.  However, once in BASIC or TEXT the 
bottom four lines do not display correctly. /(See attached.)/


/(Planned to test LCD in M102 but it has a different connector.  I 
don't have a second M100 right now to test it in, but I am 99.99% 
positive the LCD is fine)/


So I purchased a logic prob (Elenco LP-900) 
 to 
test chip select lines on the LCD connector (Pins 14, 12, 10, 8, 7, 
16,15,13,11, 9, and CS1=Pin? - /schematics blurry/).


As I unboxed it I remembered I never used one before. :)

- Where do I place the/pos/ and /neg/ alligator clips?

- Do I set the logic prob to/400PPS/ or/00.5PPS/?

- In checking the chip select lines, am I looking for /HI, LO, or PULSE/?

I see no broken or corroded lines on the board.

Thanks in advance.

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
mailto:bir...@soigeneris.com>> wrote:


This loss of an entire block is the symptom of a missing chip select. 
When the LCD driver chips are powered/reset they will drive every 
pixel on/black. When they receive the proper initialization, they will 
drive every pixel off/clear. It seems the rest and initialization 
steps are being done so commands are getting through (and the machine 
is booting so the LCD has to be initializing and responding).


Each driver chip on the LCD controls one block of pixels. If an entire 
block is missing, it is a good sign the chip select is not getting 
through. It could be a bad trace on the M100, a bad LCD cable or a bad 
LCD itself. If you have a scope of logic probe you can check to see if 
all the chip select lines are toggling.


Jeff BIrt

*From:*M100 > *On Behalf Of *Chris Fezzler

*Sent:* Wednesday, July 22, 2020 11:26 AM
*To:* m...@bitchin100.com 
*Subject:* Re: [M100] Listserv Search

Here you go.

On Wednesday, July 22, 2020, 11:52:23 AM EDT, Stephen Adolph 
mailto:twospru...@gmail.com>> wrote:


a pic of the garbled screen would be great if you can do it.. thanks


Re: [M100] Listserv Search

2020-07-26 Thread Chris Fezzler
 No after market ROM.
Logically, I would think the fact that the top four lines are perfect, the hard 
reset produces a perfect Menu screen, and just the bottom four lines are 
garbled would be a clue where to look.
I know nothing other than reading a lot off Internet.  My instinct tells me the 
issue is a component that regulates power or signals to the LCD driver chips 
for the bottom half of the screen.  The are getting power (because we see 
gibberish and the perfect Menu screen) but perhaps it is the wrong voltage or 
intermittent power or signal.
Thoughts are:
Capacitors C47 or C54 and or M17 and/or M25.
But I don't know how to determine their impact on the issue. 


On Sunday, July 26, 2020, 11:25:01 AM EDT, Jeffrey Birt 
 wrote:  
 
 
When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.

  

If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.

  

Do you have any sort of aftermarket ROM installed? 

  

Very interesting problem. 

  

Jeff Birt

  

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 9:47 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

  

Gladly.

  

  

  

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt  
wrote: 

  

  

Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) to test chip select lines on the 
LCD connector (Pins 14, 12, 10, 8, 7, 16,15,13,11, 9, and CS1=Pin? - schematics 
blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
 wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).

 

Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.

 

Jeff BIrt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Wednesday, July 22, 2020 11:26 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

Here you go.  

 

 

 

On Wednesday, July 22, 2020, 11:52:23 AM EDT, Stephen Adolph 
 wrote: 

 

 

a pic of the garbled screen would be great if you can do it.. thanks

 

On Wed, Jul 22, 2020 at 11:37 AM Chris Fezzler  wrote:


Sorry - typing too fast.  Top four lines of the screen.

 

Yes, mostly garbage all of the time.  Except a hard rest will generate a proper 
menu screen.

Yes, in BASIC the same.  But if I type in a test program and hit RUN the 
program will indeed run.

So the computer is getting the commands/keystrokes.  Just not displaying bottom 
four lines.

 

I think it is a component issue.

 

 

On Wednesday, July 22, 2020, 09:20:53 AM EDT, Stephen Adolph 
 wrote: 

 

 

Hi Chris,

 

What do you mean by "the top 4".  Do you mean top 4 lines on the screen?  I 
think so.

 

So is it correct to say that the LCD bottom  4 lines display garbage at certain 
times

* not after a (hard) reset - you get a correct MENU display  (not just a RESET 
but a HARD RESET?)

* when you enter BASIC 

Re: [M100] tranch #2 of REXCPM is off the docks!

2020-07-26 Thread Greg Swallow
Jim,

Finally got rxcini.do transferred to M100. Problem was forgetting to add my 
user to tty group. Thanks for the steps. It all pointed me in the right 
direction to see my error.

God Bless,

GregS <><

Jul 25, 2020 9:08:11 PM Jim Hart :

> Greg,
> 
> I just finished writing this up, there are likely typos but I wanted to get 
> it to you before I get sidetracked again.  Things are very busy around here. 
> E-mail me if you have any questions. I will try and improve them this week.
> 
> Linux instructions (rough draft)
> 
> -
> 
> Minicom is the "standard" in Linux terminal programs. You need a program that 
> will alllow for the binary transfer of data without a transfer protocol.  
> Minicom can be configured for thie.  To configure Minicom,  install it with 
> apt get minicom and you will also need PV, so install it also. TO actually 
> configure Minicom for binary transfers you need to create a small script 
> sendbin.sh:
> 
> -
> #!/bin/sh
> INFILE=/dev/null
> OUTFILE=/dev/null
> 
> while [ $# -gt 0 ]; do
> case "$1" in
> -i)
> shift
> INFILE="$1"
> ;;
> -o)
> shift
> OUTFILE="$1"
> ;;
> -h|--help)
> echo "$0 -i infile -o outfile"
> ;;
> *)
> INFILE="$1"
> esac
> shift
> done
> cat << EOF
> binary-xfer utility for minicom
> Sending file ${INFILE} to ${OUTFILE}
> EOF
> 
> /usr/bin/pv --force -i 0.25 -B 128  ${INFILE}  2>&1 > ${OUTFILE}
> # Use the line below if you don't have pv!
> 
> # /bin/cat ${INFILE} > ${OUTFILE}
> cat << EOF
> 
> File transfer complete
> EOF
> sleep 10
> -
> 
> Open Minicon and user -A, O to open the options menu.  From there 
> select "File Transfer Protcols", we are going to all a new selection.  Slots 
> A through I are used so select J and enter the following values
> 
> bin        /home/kimberley/scripts/sendbin.sh -o %l  Y    U    Y       N      
>  N
> 
> This will create a new protocol for transferring data directly, while passing 
> binary values without change.
> 
> Use this new option to send your file.  Connect using Telecom and press F2 
> for Download, enter the filename "rxcini.do" and press -A, S to send a 
> file in Minicom.  Select the protocol, the new one, "bin", that was just 
> added. User the left/right arrow keys and "Enter" to select "Goto" in Minicom 
> and enter the directory to which you unzipped "rxcini.DO" to.  Used the same 
> keys to select "show" to filter the files, enter "rxcini.DO" Use the up/down 
> arrow to move the pointer to the file and then the left/right arrows to 
> select "tag" to actually select the file to send. Finally, press "enter" to 
> actually send the file.  When the transfer is complete, press "F2" on the 
> M100/T102 again to stop the transfer.
> 
> RXCINI.DO loads a file from the TPDD or emulator.  Under Linux the best 
> option is Laddie Alpha under Mono.  You need to install Mono and download 
> Laddie Alphe. Laddie Alpha can be downloaded from the Bitchin100 site at 
> http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha . Now you 
> need to install Mono, Debian based systems run "sudo apt install 
> mono-complete". You also need the file RXC_11.zip.  Make a directory and 
> unzip RXC_11.zip into the directory.  Change directories to the new directory 
> and run "mono LaddieAlpha.exe /dev/ttyUSB0", replacing ttyUSB0 with the 
> device you are using.  Now follow the instructions to running RXCINI.DO in 
> the official documentation.
> 
> Classic REX functionality should now be working.
> 
> You can put Option ROM images into the same directory and use Laddie Alpha to 
> load these onto the REX also.
> 
> Grab the CP/M initialization files and the image for your sized REXCPM and 
> place these in the same directory.
> 
> Install the TS-DOS option ROM to copy the CPM.CO[http://CPM.CO] and 
> CPMUPD.CO[http://CPMUPD.CO] files to the M100/T102 from Laddie Alpha.  These 
> are the files to install the CP/M functionality.  Leave the *.BK file in the 
> directory, CPMUPD.CO[http://CPMUPD.CO] will transfer this to the REX.
> 
> Follow the instructions for CP/M on the M100/T102 found here: 
> http://bitchin100.com/wiki/index.php?title=M100_CP/M
> 
> -
> 
> --Jim
> 
> On Thu, Jul 23, 2020 at 10:54 PM Greg Swallow  wrote:
> 
>> Jim,
>> 
>> I could use your Linux help/step-by/information. Just converted my last 
>> Windows PC to elementaryOS. Am also running openSuse Tumbleweed, but am 
>> consolidating to one/two system(s).
>> 
>> Dropped an PCI 2-port RS232 in and am working on getting it working for the 
>> M100.
>> 
>> Thanks,
>> 
>> GregS <><
>> 
>> Jul 23, 2020 7:32:22 PM Jim Hart :
>> 
>>> I received mine yesterday, and after some trouble getting it initialized 
>>> (all on the Linux host), it is working great.  If anyone is having trouble 
>>> with installing the software from Linux, let me know and I can offer my 
>>> solutions.
>>>
>>> I 

Re: [M100] Listserv Search

2020-07-26 Thread Jeffrey Birt
When comparing your two pictures, after rotating them right side up, I noticed 
just now that not only do you have blank blocks but some of the characters are 
reversed.  That is really bizarre. I’m not sure if that points to a problem 
with how the LCD drivers are being configured/initialized or what data is being 
sent to them.

 

If the driver ships are outputting a built-in font here it might be a chip 
configuration issue. If the display is always bit mapped, then it would be 
something else.

 

Do you have any sort of aftermarket ROM installed? 

 

Very interesting problem. 

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Sunday, July 26, 2020 9:47 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

Gladly.

 

 

 

On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt mailto:bir...@soigeneris.com> > wrote: 

 

 

Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com  
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) 

  to test chip select lines on the LCD connector (Pins 14, 12, 10, 8, 7, 
16,15,13,11, 9, and CS1=Pin? - schematics blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
mailto:bir...@soigeneris.com> > wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).

 

Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.

 

Jeff BIrt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Chris Fezzler
Sent: Wednesday, July 22, 2020 11:26 AM
To: m...@bitchin100.com  
Subject: Re: [M100] Listserv Search

 

Here you go.  

 

 

 

On Wednesday, July 22, 2020, 11:52:23 AM EDT, Stephen Adolph 
mailto:twospru...@gmail.com> > wrote: 

 

 

a pic of the garbled screen would be great if you can do it.. thanks

 

On Wed, Jul 22, 2020 at 11:37 AM Chris Fezzler mailto:fezz...@yahoo.com> > wrote:

Sorry - typing too fast.  Top four lines of the screen.

 

Yes, mostly garbage all of the time.  Except a hard rest will generate a proper 
menu screen.

Yes, in BASIC the same.  But if I type in a test program and hit RUN the 
program will indeed run.

So the computer is getting the commands/keystrokes.  Just not displaying bottom 
four lines.

 

I think it is a component issue.

 

 

On Wednesday, July 22, 2020, 09:20:53 AM EDT, Stephen Adolph 
mailto:twospru...@gmail.com> > wrote: 

 

 

Hi Chris,

 

What do you mean by "the top 4".  Do you mean top 4 lines on the screen?  I 
think so.

 

So is it correct to say that the LCD bottom  4 lines display garbage at certain 
times

* not after a (hard) reset - you get a correct MENU display  (not just a RESET 
but a HARD RESET?)

* when you enter BASIC and/or run any software, the LCD bottom half shows 
garbage?

 

I would suggest that you run a memory test.

I doubt that you have a fundamental problem with the LCD system, nor the 
keyboard system.

 

good problem!  

 

 

 

On Wed, Jul 22, 2020 at 9:02 AM Chris Fezzler mailto:fezz...@yahoo.com> > wrote:

I'm trying to troubleshoot what components on the circuit board process 

Re: [M100] Listserv Search

2020-07-26 Thread Chris Fezzler
 Gladly.


On Sunday, July 26, 2020, 08:36:06 AM EDT, Jeffrey Birt 
 wrote:  
 
 
Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

  

Jeff Birt

  

From: M100  On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

  

ALERT: Beginner asking question.

  

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

  

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

  

  

So I purchased a logic prob (Elenco LP-900) to test chip select lines on the 
LCD connector (Pins 14, 12, 10, 8, 7, 16,15,13,11, 9, and CS1=Pin? - schematics 
blurry).

As I unboxed it I remembered I never used one before. :) 

  

- Where do I place the pos and neg alligator clips?

  

- Do I set the logic prob to 400PPS or 00.5PPS?

  

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

  

I see no broken or corroded lines on the board.  

  

Thanks in advance.

  

  

  

  

  

  

  

  

  

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
 wrote: 

  

  

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).

 

Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.

 

Jeff BIrt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Wednesday, July 22, 2020 11:26 AM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

Here you go.  

 

 

 

On Wednesday, July 22, 2020, 11:52:23 AM EDT, Stephen Adolph 
 wrote: 

 

 

a pic of the garbled screen would be great if you can do it.. thanks

 

On Wed, Jul 22, 2020 at 11:37 AM Chris Fezzler  wrote:


Sorry - typing too fast.  Top four lines of the screen.

 

Yes, mostly garbage all of the time.  Except a hard rest will generate a proper 
menu screen.

Yes, in BASIC the same.  But if I type in a test program and hit RUN the 
program will indeed run.

So the computer is getting the commands/keystrokes.  Just not displaying bottom 
four lines.

 

I think it is a component issue.

 

 

On Wednesday, July 22, 2020, 09:20:53 AM EDT, Stephen Adolph 
 wrote: 

 

 

Hi Chris,

 

What do you mean by "the top 4".  Do you mean top 4 lines on the screen?  I 
think so.

 

So is it correct to say that the LCD bottom  4 lines display garbage at certain 
times

* not after a (hard) reset - you get a correct MENU display  (not just a RESET 
but a HARD RESET?)

* when you enter BASIC and/or run any software, the LCD bottom half shows 
garbage?

 

I would suggest that you run a memory test.

I doubt that you have a fundamental problem with the LCD system, nor the 
keyboard system.

 

good problem!  

 

 

 

On Wed, Jul 22, 2020 at 9:02 AM Chris Fezzler  wrote:


I'm trying to troubleshoot what components on the circuit board process 
keystrokes and send them to the screen.

The screen and keyboard on my Model 100 are in perfect working order.  But only 
the top four are processing correctly.

 

The bottom four are displaying gibberish.  But if I type commands in BASIC, 
they work.  So again, not the keyboard or

screen but components that process the bottom half.  A hard rest will present a 
perfect menu screen. But upon entering 

an app, the bottom four lines are not getting proper signal.

 

Sorry, I'm not an electronics or computer engineer.  Just a hobbyist with a 
soldering iron and a willingness to learn.

Plan to look at Technical Reference Manual to see if I can troubleshoot.

 

On Wednesday, July 22, 2020, 01:15:25 AM EDT, John R. Hogerhuis 
 wrote: 

 

 

 

 

On Tue, Jul 21, 2020 at 5:08 PM Chris Fezzler  wrote:


Is there a way to search old Listserv messages so I can research before 
embarrass...err...I mean ask a dumb question.

 

Seriously, would like to research.


 

 

How old are we talking?

Gmane was our archive until it went down for a long time. Then it was back up 
recently but only accessible through nntp readers. Not 

Re: [M100] Listserv Search

2020-07-26 Thread Jeffrey Birt
Can you attach a picture of the cold boot screen too? 

The positive and negative clips go to a +5 and ground source on the M100 PCB 
itself. The PPS setting if ‘Pulses Per Second’ when using it as a logic pulser, 
i.e. to inject a pulsing signal. On the chip select lines you should she them 
quickly toggling.

 

Jeff Birt

 

From: M100  On Behalf Of Chris Fezzler
Sent: Saturday, July 25, 2020 6:20 PM
To: m...@bitchin100.com
Subject: Re: [M100] Listserv Search

 

ALERT: Beginner asking question.

 

Reminder: Upon hard reset the LCD initializes perfectly and displays the main 
Menu screen perfectly.  However, once in BASIC or TEXT the bottom four lines do 
not display correctly.  (See attached.)

 

(Planned to test LCD in M102 but it has a different connector.  I don't have a 
second M100 right now to test it in, but I am 99.99% positive the LCD is fine)

 

 

So I purchased a logic prob (Elenco LP-900) 

  to test chip select lines on the LCD connector (Pins 14, 12, 10, 8, 7, 
16,15,13,11, 9, and CS1=Pin? - schematics blurry).

As I unboxed it I remembered I never used one before. :) 

 

- Where do I place the pos and neg alligator clips?

 

- Do I set the logic prob to 400PPS or 00.5PPS?

 

- In checking the chip select lines, am I looking for HI, LO, or PULSE?

 

I see no broken or corroded lines on the board.  

 

Thanks in advance.

 

 

 

 

 

 

 

 

 

On Wednesday, July 22, 2020, 02:29:39 PM EDT, Jeffrey Birt 
mailto:bir...@soigeneris.com> > wrote: 

 

 

This loss of an entire block is the symptom of a missing chip select. When the 
LCD driver chips are powered/reset they will drive every pixel on/black. When 
they receive the proper initialization, they will drive every pixel off/clear. 
It seems the rest and initialization steps are being done so commands are 
getting through (and the machine is booting so the LCD has to be initializing 
and responding).

 

Each driver chip on the LCD controls one block of pixels. If an entire block is 
missing, it is a good sign the chip select is not getting through. It could be 
a bad trace on the M100, a bad LCD cable or a bad LCD itself. If you have a 
scope of logic probe you can check to see if all the chip select lines are 
toggling.

 

Jeff BIrt

 

From: M100 mailto:m100-boun...@lists.bitchin100.com> > On Behalf Of Chris Fezzler
Sent: Wednesday, July 22, 2020 11:26 AM
To: m...@bitchin100.com  
Subject: Re: [M100] Listserv Search

 

Here you go.  

 

 

 

On Wednesday, July 22, 2020, 11:52:23 AM EDT, Stephen Adolph 
mailto:twospru...@gmail.com> > wrote: 

 

 

a pic of the garbled screen would be great if you can do it.. thanks

 

On Wed, Jul 22, 2020 at 11:37 AM Chris Fezzler mailto:fezz...@yahoo.com> > wrote:

Sorry - typing too fast.  Top four lines of the screen.

 

Yes, mostly garbage all of the time.  Except a hard rest will generate a proper 
menu screen.

Yes, in BASIC the same.  But if I type in a test program and hit RUN the 
program will indeed run.

So the computer is getting the commands/keystrokes.  Just not displaying bottom 
four lines.

 

I think it is a component issue.

 

 

On Wednesday, July 22, 2020, 09:20:53 AM EDT, Stephen Adolph 
mailto:twospru...@gmail.com> > wrote: 

 

 

Hi Chris,

 

What do you mean by "the top 4".  Do you mean top 4 lines on the screen?  I 
think so.

 

So is it correct to say that the LCD bottom  4 lines display garbage at certain 
times

* not after a (hard) reset - you get a correct MENU display  (not just a RESET 
but a HARD RESET?)

* when you enter BASIC and/or run any software, the LCD bottom half shows 
garbage?

 

I would suggest that you run a memory test.

I doubt that you have a fundamental problem with the LCD system, nor the 
keyboard system.

 

good problem!  

 

 

 

On Wed, Jul 22, 2020 at 9:02 AM Chris Fezzler mailto:fezz...@yahoo.com> > wrote:

I'm trying to troubleshoot what components on the circuit board process 
keystrokes and send them to the screen.

The screen and keyboard on my Model 100 are in perfect working order.  But only 
the top four are processing correctly.

 

The bottom four are displaying gibberish.  But if I type commands in BASIC, 
they work.  So again, not the keyboard or

screen but components that process the bottom half.  A hard rest will present a 
perfect menu screen. But upon entering 

an app, the bottom four lines are not getting proper signal.

 

Sorry, I'm not an electronics or computer engineer.  Just a hobbyist with a 
soldering iron and a willingness to learn.

Plan to look at Technical Reference Manual to see if I can troubleshoot.

 

On Wednesday, July 22, 2020, 01:15:25 AM EDT, John R. Hogerhuis 
mailto:jho...@pobox.com> > wrote: 

 

 

 

 

On Tue, Jul 21, 2020 at 5:08 PM Chris Fezzler mailto:fezz...@yahoo.com> > wrote:

Is there a way to search old Listserv messages so I can research before