Re: [M100] Rex startup time

[J.T.]

Solved, I found 1 pin with a cold joint, reflowed it, reloaded the rex software 
and everything now works :)    Thanks!

Re: [M100] Rex startup time

[Josh Malone]

Yeah, it takes a fair amount of cleanup, still. I'm sure that some other
board house can do castellation but they might have a min order that would
require a group buy to meet.

On Mon, May 14, 2018, 5:30 PM Stephen Adolph  wrote:

>
> "   OSH are not really set up to build castellated boards it does work but
> needs extensive cleanup especially if they put the mouse bites on the
> castellated edge :("
>
> you arent kidding.  disappointed in my last 3 boards.
>
>

Re: [M100] Rex startup time

[Stephen Adolph]

"   OSH are not really set up to build castellated boards it does work but
needs extensive cleanup especially if they put the mouse bites on the
castellated edge :("

you arent kidding.  disappointed in my last 3 boards.

Re: [M100] Rex startup time

[Josh Malone]

On Mon, May 14, 2018 at 3:21 PM, Stephen Adolph  wrote:
> One could take the pen and write some software to test REX.

Sounds like a good idea! I think I'd have to have a better idea how
the software worked first, but I'm intrigued. I might start work on a
design for this.

-Josh

Re: [M100] Rex startup time

[John R. Hogerhuis]

On Mon, May 14, 2018 at 12:21 PM Stephen Adolph 
wrote:

> One could take the pen and write some software to test REX.
>
>
Agree that would be better than a document.

>From my point of view I wouldn’t encourage most people to be DIYing a rex.
Leave it to a few people that want to take responsibility for fully testing
the units they distribute.

One way or another that seems like it would work.

— John.

Re: [M100] Rex startup time

[John R. Hogerhuis]

Yeah makes sense.

Whatever instructions DIYers are following need to have some clear
verification / validation steps.

— John.

Re: [M100] Rex startup time

[Stephen Adolph]

One could take the pen and write some software to test REX.


On Mon, May 14, 2018 at 3:21 PM, John R. Hogerhuis  wrote:

> Yeah makes sense.
>
> Whatever instructions DIYers are following need to have some clear
> verification / validation steps.
>
> — John.
>

Re: [M100] Rex startup time

[Josh Malone]

Yes, if a known-good REX has REXMGR issues, it's probably operator
error or socket contact.

However, having built lots of REXes, I recognize these symptoms as a
bad flash load, and that's usually caused by assembly issues (or, at
least, is usually rectified by rework). The CPLD load can be verified
using iMPACT, but the flash load is *not* verified as part of the
programming process; the only way I know to verify the flash load is
the REXMGR checksum and by that point, REXMGR is already running and
that's a very strong indication that the flash load is correct :)


On Mon, May 14, 2018 at 12:02 PM, John R. Hogerhuis  wrote:
> The simplest reasons for REX to fail are not installing REXMGR with the CALL
> or poor contact between REX and the option rom bay.
>
> But I’m spoiled by always using a REX that was known good / tested at some
> point (by Steve).
>
> — John.

Re: [M100] Rex startup time

[John R. Hogerhuis]

The simplest reasons for REX to fail are not installing REXMGR with the
CALL or poor contact between REX and the option rom bay.

But I’m spoiled by always using a REX that was known good / tested at some
point (by Steve).

— John.

Re: [M100] Rex startup time

[Josh Malone]

> Just got done constructing and installing a REX using build 162. The flash
> of the Xilinx and the loading of the Rex software via Tpdd went smooth. It
> all looks right up until I actually try to do the call 63012.  The Rex is
> installed in a 32k model 100 and the previous option rom worked flawlessly,
> so I know the socket works properly.  So how long does the REX take to
> start? Am I just being impatient ?

There's probably either a) a solder bridge on the flash chip; or b)
too much flux residue on the board (again, esp around the flash). If
you didn't clean the PCB with alcohol, do that first. Then re-flash
the REXMGR (no need to do the CPLD) and re-test. Failing that, you'll
need to re-flow the solder. On one of my early boards, I actually had
to go as far as to remove the flash chip, clean the flux from
underneath it (I was using too much when I first got started building)
and re-install it with less flux to get it working.

-Josh

Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 100

[Fugu ME100]

That’s great.   Pleased to hear you tracked it down - another 100 survives  :)  
Now you have two and that’s how it all starts….

If you want to build RAM modules for the M100 I have two RAM PCBs on OSH Park: 
SMD Version and DIP version.   The design is based on the old NEC modules.
https://oshpark.com/shared_projects/V0tpeuMg
https://oshpark.com/shared_projects/Ra3VwoJo

There are a few different options to add pins to the PCBs for mounting.

From: M100 
> 
on behalf of Jeffrey Birt >
Reply-To: >
Date: Sunday, May 13, 2018 at 6:52 PM
To: >
Subject: Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 
100

Update…

It was the RAM module. After thinking about it after Fugu’s email the other day 
it occurred to me I had done a capture of the standard RAM bank select lines 
(and I happened to dave it) and after looking at it again it looked fine. This 
evening I pulled the standard RAM module out, split apart a 30 pin DIP socket 
to make two 15 pin SIPs and plugged in of the option RAMs. AND…nothing. Sigh…

Then I noticed I had not plugged the ROM back in after cleaning the flux from 
the board. So, the ROM was installed, and STRL-BRK done on power up and…It’s 
ALIVE! Bwa-ha-ha-ha! It’s ALIVE!

I tried reflowing the original standard RAM module and it still did not work. I 
could ohm out each line to each individual RAM chip and maybe get lucky and 
find one open trace, but I would guess that a bad RAM chip is more likely. I’ll 
look into making some more RAM module or buying a few, for now I have 16K.

As luck would have it the second M100 I bought from across the state arrived 
yesterday, I still have not opened it yet. It is supposed to work, got it from 
the original owner who seemed like a nice guy. A grand total of $61 including 
shipping. Now I’ll put together an order for enough caps to finish recapping 
the first M100 and re-cap the 2nd one while I’m at it. I also need to try and 
calculate a super-cap size that will at least match the original NiCad battery.

Thanks again everyone (especially Fugu) for your help.

Jeff

Re: [M100] Rex startup time

[Fugu ME100]

After CALL 63012 the return to the menu with REXMGR loaded should take ~1s it 
is almost instant.   You may also want to try a cold boot just in case 
something is in the RAM.

If it is hanging (and the board is installed correctly) then there is most 
likely a dry/bad joint on the Flash memory or Xliinx part.  The module can 
appear to program OK even with dry/bad joints.   When programming with V4.9, as 
it clears the Flash memory the block count should take about 1s/block to clear. 
 If it is faster than that the module will fail, similarly when copying the REX 
software to block 0 it should not be instant.

Probably best to inspect the soldering to make sure there are no bridges or bad 
joints.  A magnifying glass and dental pick are good tools for the inspection 
process.  Double check the part orientation too.If the module is based on 
the OSH board then check there is no copper flashing across the board edge 
pins, the routing process during manufacture can cause pin shorts along the 
side.   OSH are not really set up to build castellated boards it does work but 
needs extensive cleanup especially if they put the mouse bites on the 
castellated edge :(

From: M100 
> 
on behalf of "J.T." >
Reply-To: >
Date: Monday, May 14, 2018 at 6:12 AM
To: "m100@lists.bitchin100.com" 
>
Subject: [M100] Rex startup time


Just got done constructing and installing a REX using build 162. The flash of 
the Xilinx and the loading of the Rex software via Tpdd went smooth. It all 
looks right up until I actually try to do the call 63012.  The Rex is installed 
in a 32k model 100 and the previous option rom worked flawlessly, so I know the 
socket works properly.  So how long does the REX take to start? Am I just being 
impatient ?

Sent from Yahoo Mail for 
iPhone

[M100] Rex startup time

[J.T.]

Just got done constructing and installing a REX using build 162. The flash of 
the Xilinx and the loading of the Rex software via Tpdd went smooth. It all 
looks right up until I actually try to do the call 63012.  The Rex is installed 
in a 32k model 100 and the previous option rom worked flawlessly, so I know the 
socket works properly.  So how long does the REX take to start? Am I just being 
impatient ?

Sent from Yahoo Mail for iPhone

Re: [M100] use of PRINT

[VANDEN BOSSCHE JAN]

I would never use a ‘+’ in a print statement. It is an extra concatenation 
action, which is unnecessary in a print. Use ; instead.

With that in mind, I would write Stephen’s code as followes:

10 PRINTE;"pFile to Convert ";E;"q";
And for George:

PRINT CR$;CHR$(Y);CHR$(X);

Actually, what does CHR$(27)+CHR$(89) do ?

FWIW, I always used print@ to position the cursor. So, that code would become:

Y=3REM line numbers from 0-7
X=14   REM positions from 0-39
PRINT@(Y*40+X),;

That works everywhere, except for the last position on screen, where Y=7 and 
X=39 .

Ah well, the finesses/limitations of BASIC.

Greetings from the TyRannoSaurus / Jan-80@work

From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of George 
Rimakis
Sent: zondag 13 mei 2018 16:12
To: m...@bitchin100.com
Subject: Re: [M100] use of PRINT

Hi Stephen,

It’s funny you sent this, I was about to post. I’m trying to use the Escape 
Sequences to reposition the cursor to the location of Y,X.

I’ve got

Y=3
X=14
CR$=CHR$(27)+CHR$(89)
PRINT CR$+CHR$(Y)+CHR$(X);

I’ve already turned on the cursor earlier.

Do I just have the wrong syntax? I also noticed that the strings to concatenate 
without use of + while testing this.

~Geore\ge

From: M100  on behalf of Stephen Adolph 

Reply-To: 
Date: Sunday, May 13, 2018 at 10:08 AM
To: 
Subject: [M100] use of PRINT

I found this interesting bit of code.
here E=chr$(27).

10 PRINTE"pFile to Convert "E"q";
I didn't know that basic automatically concatenates strings like this.  I would 
have written this
10 PRINT E+"p"+"File to Convert"+E+"q";

VIVAQUA et HYDROBRU ont fusionné.
VIVAQUA est votre société d'eau en Région de Bruxelles-Capitale.

VIVAQUA en HYDROBRU zijn gefusioneerd.
VIVAQUA is uw waterbedrijf in het Brusselse Hoofdstedelijk Gewest.

[http://www.vivaqua.be/facebook.png] Rejoignez-nous sur Facebook - Volg ons op 
Facebook

DISCLAIMER
Pensez à l'environnement, n'imprimez cette page et ses annexes que si c'est 
nécessaire. Ce message électronique, y compris ses annexes, est confidentiel et 
réservé à l’attention de son destinataire.  Si vous n'êtes pas le destinataire 
de ce message, merci de le détruire et d’en informer l’expéditeur. Toute 
divulgation, copie ou utilisation de ce mail est dans ce cas interdite. La 
sécurité et l'exactitude des transmissions de messages électroniques ne peuvent 
être garanties.
Denk aan het milieu; druk deze pagina en de bijlagen alleen af als het nodig 
is. Dit e-mailbericht (inclusief zijn bijlagen) is vertrouwelijk en is 
uitsluitend bestemd voor de geadresseerde. Als dit bericht niet voor u bestemd 
is, wordt u verzocht het te wissen en de afzender te informeren. Het is in dat 
geval niet toegestaan dit bericht te verspreiden, te kopiëren of te gebruiken. 
We kunnen niet garanderen dat de gegevensoverdracht via het internet veilig en 
nauwkeurig is.