Return-Path: Delivered-To: craig@sbc-85.com Received: from gator4254.hostgator.com by gator4254.hostgator.com with LMTP id IG0fNSZzy2WyNQ8AcizydQ (envelope-from ) for ; Tue, 13 Feb 2024 07:48:22 -0600 Return-path: Envelope-to: craig@sbc-85.com Delivery-date: Tue, 13 Feb 2024 07:48:22 -0600 Received: from mout.perfora.net ([74.208.4.194]:43123) by gator4254.hostgator.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1rZt94-004DFS-1E for craig@sbc-85.com; Tue, 13 Feb 2024 07:48:22 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elavsky.net; s=s1-ionos; t=1707832091; x=1708436891; i=tom@elavsky.net; bh=wM/ALWwKWoI1odSXcxTnV9Y8av7vQ9iSZ58tAwNZHoM=; h=X-UI-Sender-Class:From:To:Subject:Date:References:In-Reply-To; b=GmTGsA+UjACpJQy2dPaQh2UaRn3tA/pl8SlyQYRmVUWOSEOTPKRppT4Xi1d49t9d OBJhwA5kxY8t6cjkIxl9M4G4xw49SeM2gfMeUBUMaCmmmnsRazMLLDrd703z/qc9R 0rOUpCpAabilPzhidFjVO/1ewE4HbgiAe1OpsIdDDewdlNYu/7Y7/xh/uFin0lCq/ wlmuiN2KoXa9lMZDNkS4T/3vyc8dDAYG2w9xx//tOVcVQ4E3Groqq4VtkzegldkLL yqAAGy4Nqua5I7TYqx4f4ymOtKsNmihhYn+hPb/pszXfJL80zYAigHZk/NnzYYOs0 NIftKhX515dYPU/b4A== X-UI-Sender-Class: 55c96926-9e95-11ee-ae09-1f7a4046a0f6 Received: from CH3PR20MB6832.namprd20.prod.outlook.com ([40.99.231.53]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Ln8sF-1r3qdi1r7V-00hQIF for ; Tue, 13 Feb 2024 14:48:11 +0100 From: "tom@elavsky.net" To: "craig@sbc-85.com" Subject: Re: MCS-85+ No Communications Thread-Topic: MCS-85+ No Communications Thread-Index: AQHaXPyPpJ+D+YmxlEuCATXojtraxbEGUYwAgABvItGAAIXIgIABBV4/ X-MS-Exchange-MessageSentRepresentingType: 1 Date: Tue, 13 Feb 2024 13:48:10 +0000 Message-ID: References: <134301da5d85$c3bb0c60$4b312520$@sbc-85.com> <14a601da5e00$38e9d370$aabd7a50$@sbc-85.com> In-Reply-To: <14a601da5e00$38e9d370$aabd7a50$@sbc-85.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 msip_labels: Content-Type: multipart/alternative; boundary="_000_CH3PR20MB68329FB2D56469C2B3E68B31AD4F2CH3PR20MB6832namp_" MIME-Version: 1.0 X-Provags-ID: V03:K1:9My95CKqeoKuje/ytF4jVTs7Hojvn1lG8rv+RvVdqD7HCW2ptpd rOD9SYYKfGHirh2tYowF7F/s8ZWkzTM6WELciV9srTHctMZYy1650Ox8FmhgrUlLUPKIlxa 8myNxn1u0F0d7JtJgZs2b4JPtphkss95HBZX1P7tYxP6kBlhELLvjkjI1lk0cogOQw9ITzn oWsFbdbZ+EO5dkLWGamMg== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:NzN5n2LhH/c=;jDl3pRgBG5wQij1bG2cwsvKEgfY CmtRlgwJCCRUcjRXnGyVtnkj/x+Rwfwacq6s+lStpsNZmMYdhnfhZI2ndsKvFStZYrZxtxhMZ r2mtWsByPfSyvouPeFEBefDlSnVwCkchhgefzOrTw/kK4zAlNvohLLf6FScQ87VKzal3z5wzk DKZfKvmrNbSDl+1JarVD8xebXpfUPktEmqOol5JZqLV1T9z5WOCi+z/djV3U7Bq4xRJM6w9JL EI5fmihEpcEVfb8ZuO2WQeV59QlXsITrAIfReYci44gywHwB3PT9fCZmse4g2DAjg5LeCZ1Ny OL0kx8zMPE7hYwLch0zx0dli410S2aLf7LYyYv3QbKeo0XJUav7k75JniYbKKUIHjX0F6ecWy nb4SaqMavLqnOOSVV6kccos7mNWgKWdbAvRUrn4++MnYm1c/Say9OIVUf8JaDahnu02GMqd42 7tDR8qlYiP1J6Vwk7ibVK/xC1IXrbZ4F8adnFvnIOmgl3m8vvrxof60VDBSre34PKET63qAzh De1hsbuaho2O3TFtwX5tMZpAVycKqwlqsYr8CpN9XYmWQU7g+jX0u1ac1VbHRlQIMXKsLIC7E ZZ3YdjMbAh4OwV/4JgifJw7gASSqwZ3leZV9qwhuGrPEAsOTJGvG/VDaOplPvSFFzL4iLuJYk keYUbrpWCBkFMR96P3O5AM7EEvBJkMx46aGUTblu32dwtfl60g85knW74ay1njqO7ZmfVgP/E y9HPktSR2GmEGwNNO1KersiqC4ZVUjK6TCKNifcT+LDBWDMYaxF56s= X-Spam-Status: No, score=-0.7 X-Spam-Score: -6 X-Spam-Bar: / X-Spam-Flag: NO --_000_CH3PR20MB68329FB2D56469C2B3E68B31AD4F2CH3PR20MB6832namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Craig, That sounds good. Everything looks to be working well. And I do want to l= earn more learn more with the assembler code, so assembling code and trying= the accept command is of interest to me. Thank you again for your help! Regards, Tom ________________________________ From: craig@sbc-85.com Sent: Monday, February 12, 2024 2:09 PM To: tom@elavsky.net Subject: RE: MCS-85+ No Communications Hi Tom, It looks like the version of the monitor I am running now on my MCS-85+ is = v0.0.9 As far as differences, I have increased the baud rate but that appears to b= e the only thing that actually changes the functionality of the code. The = monitor description and function remains the same as in the latest version = of the user=92s manual (aug 22, 2023 date in the footer). Since you have the assembler running, you should be able to assemble code a= nd then download the hex file into RAM using the A command. Of course you = can also create programs and burn into another 8755 directly. Regards craig From: tom@elavsky.net Sent: Monday, February 12, 2024 6:34 AM To: craig@sbc-85.com Subject: Re: MCS-85+ No Communications Hi Craig, My trouble shooting. The loop back with Tx & Rx worked. I tested all the = pins I could identify as stopping the 8085 with my voltmeter and all seemed= corrected. I finally pulled the 8085 out of my working SDK-85 System Desi= gn Kit board & replaced the 8085 on the MCS-85+ board, and with some playin= g around, the unit started communicating. See attached screenshot. I was g= etting gibberish on Tera Term VT at 9600 baud, but when I changed it to 240= 0 baud, it is now working. The conclusion is the 8085 was bad. The hex file from your zip file I burned into the 8755A EPROM was iSDK_85+1= 21.hex. I'm not sure what value to compare with iSDK_85+121.lst? As an experiment I did take the iSDK_85+121.A85 code and use the A85 assemb= ler, doing "a85 iSDK_85+121.A85 -o iSDK_85+121.hex" in the command window. = It said there were 27 errors, and when I compared the iSDK_85+121 hex file= you sent to the results I got, there was one line in the hex listing that = was a string of zeros and the last several digits were different. Can you tell me if I have the correct monitor for the MCS-85+ board? I am = happy that at least I have something working. Thank you & best regards, Tom ________________________________ From: craig@sbc-85.com > Sent: Sunday, February 11, 2024 11:33 PM To: tom@elavsky.net > Subject: RE: MCS-85+ No Communications Hi Tom, Looking at this before I went to bed I noticed the hex listing. That is no= t the SDK monitor, it is a diagnostic monitor. I don=92t think you properl= y burnt the 1.21 version of the monitor that I sent a few days ago in a zip= file. Check again and compare to the address contents in your buffer or eprom to = the value in the .lst file in that zip. Regards craig From: tom@elavsky.net > Sent: Sunday, February 11, 2024 7:20 AM To: craig@sbc-85.com Subject: MCS-85+ No Communications Hi Craig, I'm looking for some help if you have time. I have been able to get the MC= S-85+ board assembled. (Front and back pictures attached for reference, sh= owing jumpers.) I programmed an 8755A EPROM with iSDK_85+121. (ASCII text= printout attached.) And I set up using Tera Term VT. (Screen shots attac= hed.) I've tried different settings in Tera Term, but no luck. I have ord= ered additional 8085s and 8156s to try. If you see something I have done w= rong, please let me know. Thank you and best regards, Tom Elavsky --_000_CH3PR20MB68329FB2D56469C2B3E68B31AD4F2CH3PR20MB6832namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hi Craig,

That sounds good.  Everything looks to be working well.  And I do= want to learn more learn more with the assembler code, so assembling code = and trying the accept command is of interest to me.

Thank you again for your help!

Regards,

Tom
From: craig@sbc-85.com <= craig@sbc-85.com>
Sent: Monday, February 12, 2024 2:09 PM
To: tom@elavsky.net <tom@elavsky.net>
Subject: RE: MCS-85+ No Communications
 

Hi Tom,

 

It looks like the version of the monitor I am runn= ing now on my MCS-85+ is v0.0.9

As far as differences, I have increased the baud r= ate but that appears to be the only thing that actually changes the functio= nality of the code.  The monitor description and function remains the = same as in the latest version of the user=92s manual (aug 22, 2023 date in the footer).

Since you have the assembler running, you should b= e able to assemble code and then download the hex file into RAM using the A= command.  Of course you can also create programs and burn into anothe= r 8755 directly.

 

Regards

craig

 

 

 

From: tom@elavsky.net <tom@elavsky.net&g= t;
Sent: Monday, February 12, 2024 6:34 AM
To: craig@sbc-85.com
Subject: Re: MCS-85+ No Communications

 

Hi Craig,

 

My trouble shooting.  The loop b= ack with Tx & Rx worked.  I tested all the pins I could identify a= s stopping the 8085 with my voltmeter and all seemed corrected.  I finally pulled the 8085 out of my working SDK-85 System Design Kit board= & replaced the 8085 on the MCS-85+ board, and with some playing around= , the unit started communicating. See attached screenshot.  I was gett= ing gibberish on Tera Term VT at 9600 baud, but when I changed it to 2400 baud, it is now working.  The conclusio= n is the 8085 was bad.

 

The hex file from your zip file I bur= ned into the 8755A EPROM was iSDK_85+121.hex.  I'm not sure what value= to compare with iSDK_85+121.lst?

 

As an experiment I did take the iSDK_= 85+121.A85 code and use the A85 assembler, doing "a85 iSDK_85+121.A85 = -o iSDK_85+121.hex" in the command window.  It said there were 27 errors, and when I compared the iSDK_85+121 hex file you sen= t to the results I got, there was one line in the hex listing that was a st= ring of zeros and the last several digits were different. 

 

Can you tell me if I have the correct= monitor for the MCS-85+ board?  I am happy that at least I have somet= hing working.

 

Thank you & best regards,<= /p>

 

Tom

From: craig@sbc-85.com <craig@sbc-= 85.com>
Sent: Sunday, February 11, 2024 11:33 PM
To: tom@elavsky.net <tom= @elavsky.net>
Subject: RE: MCS-85+ No Communications

 

Hi Tom,

Looking at this before I went to bed I noticed th= e hex listing.  That is not the SDK monitor, it is a diagnostic monito= r.  I don=92t think you properly burnt the 1.21 version of the monitor= that I sent a few days ago in a zip file. 

 

Check again and compare to the address contents i= n your buffer or eprom to the value in the .lst file in that zip.

 

Regards

craig

 

 

 

 

Hi Craig,

 

I'm looking for some help if you hav= e time.  I have been able to get the MCS-85+ board assembled.  (F= ront and back pictures attached for reference, showing jumpers.)  I programmed an 8755A EPROM with iSDK_85+121.  (ASCII text printout a= ttached.)  And I set up using Tera Term VT.  (Screen shots attach= ed.)  I've tried different settings in Tera Term, but no luck.  I= have ordered additional 8085s and 8156s to try.  If you see something I have done wrong, please let me know.

 

Thank you and best regards,

 

Tom Elavsky 

--_000_CH3PR20MB68329FB2D56469C2B3E68B31AD4F2CH3PR20MB6832namp_--