From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_05,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.5-pre1 X-Received: by 2002:a0c:99c8:: with SMTP id y8mr22620093qve.100.1595849667711; Mon, 27 Jul 2020 04:34:27 -0700 (PDT) X-Received: by 2002:a05:620a:62f:: with SMTP id 15mr21371436qkv.483.1595849667477; Mon, 27 Jul 2020 04:34:27 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!feeder1.feed.usenet.farm!feed.usenet.farm!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 27 Jul 2020 04:34:26 -0700 (PDT) In-Reply-To: <62b1618d-e93d-42f4-9970-314685e2c01ao@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: google-groups.googlegroups.com; posting-host=203.59.139.151; posting-account=d51RWwoAAADvR-x0zYAtT9z3CRxT1eXo NNTP-Posting-Host: 203.59.139.151 References: <748b7abb-4bda-4174-aa37-367daaf1c02ao@googlegroups.com> <6cbf26a5-2047-4685-a87b-381bc5fedd5bo@googlegroups.com> <4472b2d0-e872-46c9-8665-af1fea1cc8c4n@googlegroups.com> <62b1618d-e93d-42f4-9970-314685e2c01ao@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: SweetAda 0.1e released From: Roger Mc Injection-Date: Mon, 27 Jul 2020 11:34:27 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:59546 List-Id: On Monday, July 27, 2020 at 8:51:55 PM UTC+10, gabriele.g...@gmail.com wrot= e: > On Sunday, July 26, 2020 at 3:51:41 AM UTC+2, Roger Mc wrote:=20 > > I reinstalled 0.1e and now it works, at least to the extent that 0.1d w= orks.=20 > > Quite strange as I had the same problem on both my computers.=20 > > The only thing that I can think of is that on the previous 01e install = I just used=20 > > ./menu.sh ( without target selection)=20 > > which was the method I used for 0.1d. Perhaps this messed something up?= =20 > > When that didn't work, I inspected 0.1e menu.sh and discovered the need= to use target selection;=20 > > however, on using target selection, in the order stated in your advice = (perhaps eventually), I had the reported problem.=20 > > It seems, somehow I messed something up; somehow on both computers!=20 > > Thanks for your much appreciated advice.=20 > >=20 > > I still haven't tracked down the Catalina problem. Inspiration comes sl= owly.=20 > > Certainly, the Ada code is working correctly but, somehow the assembly = coded outb instructions in x86_64-io don't seem to be having any effect.=20 > > Possibly being blocked by Catalina security features?=20 > > I currently don't know how to track outb functionality.=20 > > I'll keep trying (slooowly) > Hi Roger.=20 >=20 > Fine, the most important thing is that we have verified that tools run co= rrectly. Maybe it could be useful to delete everything (after a backup) and= repeat a fresh installation, so you could check that you have a perfectly = aligned layout, without previous mistakes.=20 > I just received your message recommending awaiting the next release.=20 > Correct me if I'm wrong, I understood that IOEMU window is working and sh= ows I/O widgets cycling, but not in Catalina, is that correct?=20 Thats correct. I had the IOEMU window working and showing I/O widgets cycl= ing under High Sierra but still not under Catalina. >=20 > In this case maybe there is either a problem in the GUI code or in Catali= na handling of windows.=20 >=20 > But you can assume safely that Ada code is working since you should see s= ome output in serial terminal.=20 Yes I'm very confident that the Ada code is working and certainly see outp= ut in the serial terminal and the QEMU window. >=20 > About the outb instruction, please explain me (even writing down your cod= e) what you are trying to do. outb instructions should behave fine, otherwi= se you should see a totally dead system.=20 The outb instructions that I was referring to are those in X86_64-io.adb wh= ich are invoked by pc.PIC procedures which I have been trying to understand= . My current understanding is that it is PIC procedures in pc.adb that should= drive the I/O widgets cycling in the IOEMU window via the in X86_64-io o= utb instructions? >=20 > By the way, apologies if I repeat myself, but try to isolate your code in= an application file like the standard one, I'm changing some with/use and = simplify units, so expect some minor changes in future release. This way yo= u can change very little in your code. For example, unit x86_64.IO is likel= y to change in CPU.IO. Ask me if you have difficulties recompiling your cod= e.=20 Understood. But, at the moment I'm nowhere near producing my own code and a= m essentially trying to "reverse engineer" your code in order to understand= how things work. I have spent today coming to grips with MPLAB via various MPLAB tutorials, = which also included tutorials on PIC hardware and interfacing. This, event= ually has been quite rewarding but I still have some way to go to reach ade= quate knowledge. I've not tried sending files via Google Groups before so I don't know if th= is works! If it does this shows my current understanding of the system /System/Volumes/Data/QEMU/sweetada_run.pdf.zip