Solved: Odd behavior with a STorm-ST board?

[rubber_jonnie]

So what was the actual problem?

[Darklord]

Okay, I've heard back from the team and there won't be any uploads until they
are sure it's safe for public consumption and if they do decide to do a general
release, it will be through their regular channels.

Thanks all.

[Darklord]

So what was the actual problem?

Sorry - Holger adapted the original ALTRAMON.PRG that goes in the AUTO folder.

Here is how Holger explained it to me when I asked about it:

-----------------------------------------------------------------------------------------

"Step2 involves to access a specific register inside the memory chip.

It requires a kind of unlock procedure, a special sequence of specific accesses.

But it seems the memory chip is somehow miscounting the steps of the unlock procedure and stays locked.

I suspect this is due to signal integrity of UDS, LDS and AS signal lines, namely to much overshoot/undershoot.

But luckily this is no problem, since step1 has already made all necessary initialializations.

So instead of step2 we are doing step1.5, a short read/write test on the memory chip to confirm the proper initialialization."

-----------------------------------------------------------------------------------------

Hope this helps. I'm just really excited that it's working as intended now.

Again, just can't give enough credit to Holger Zimmerman and the ThunderSTorm team for their efforts.


PS Just curious - is anyone else out there using a STorm-ST with a 68030? I have yet
to here anyone join in on the conversation since I posted in various places about my
problem.

[rubber_jonnie]

So what was the actual problem?

Sorry - Holger adapted the original ALTRAMON.PRG that goes in the AUTO folder.

Here is how Holger explained it to me when I asked about it:

-----------------------------------------------------------------------------------------

"Step2 involves to access a specific register inside the memory chip.

It requires a kind of unlock procedure, a special sequence of specific accesses.

But it seems the memory chip is somehow miscounting the steps of the unlock procedure and stays locked.

I suspect this is due to signal integrity of UDS, LDS and AS signal lines, namely to much overshoot/undershoot.

But luckily this is no problem, since step1 has already made all necessary initialializations.

So instead of step2 we are doing step1.5, a short read/write test on the memory chip to confirm the proper initialialization."

-----------------------------------------------------------------------------------------

Hope this helps. I'm just really excited that it's working as intended now.

Again, just can't give enough credit to Holger Zimmerman and the ThunderSTorm team for their efforts.


PS Just curious - is anyone else out there using a STorm-ST with a 68030? I have yet
to here anyone join in on the conversation since I posted in various places about my
problem.

Cool thanks, I was interested form the PoV of getting the info out there for all to see

[Darklord]

Oh yes, I'm a big fan of sharing everything, all the time, everywhere.

I'm still curious though, as to whether or not anyone else is using a STorm-ST
board with a faster processor (68020/68030/etc) besides me.

I mean, I just don't recall anyone mentioning or posting anywhere about the
same problems I was seeing (at least, in any of the forums I visit).