Re: SweetAda 0.1e released

[gabriele.galeotti.xyz@gmail.com]

On Sunday, July 26, 2020 at 3:51:41 AM UTC+2, Roger Mc wrote:
> On Sunday, July 26, 2020 at 2:17:42 AM UTC+10, gabriele.g...@gmail.com wrote:
> > On Saturday, July 25, 2020 at 3:44:57 PM UTC+2, Roger wrote:
> > > On Thursday, July 23, 2020 at 4:03:06 AM UTC+10, gabriele....@gmail.com wrote: 
> > > > Hi all. I've just released SweetAda 01.e. 
> > > > 
> > > > Go to http://www.sweetada.org and download the archive. RTS and LibGCC packages are still valid @ 0.1c. 
> > > > 
> > > > - general cleanup and cosmetics 
> > > > - general infrastructure improvements 
> > > > - QEMU-RISC-V-32 target can do serial output in a terminal 
> > > > - IntegratorCP target uses LCD VGA 
> > > > - Malta MIPS target uses a VGA PCI board 
> > > > - handling of directories in the cpus hierarchy, which allows selective unit overriding 
> > > > - Insight can be called as a toolchain component 
> > > > - IOEMU configuration files are now fully consistent 
> > > > 
> > > > Next days I will to concentrate on generic low-level CPU support, documentation, and restructuring of some redundant units. Let me know, feedback is highly appreciated. 
> > > > 
> > > > G 
> > > I have not been able to build with 1e menu.sh. 
> > > The make case statement in menu.sh seems to not get activated. 
> > > In particular, no kernel.cfg file is generated. 
> > > I copied the make statements from 1d into the 1e menu.sh and make occurred until: 
> > > 
> > > [RANLIB] libplatform.a 
> > > [GPRBUILD-C] build.gpr 
> > > [GPRBUILD-B] build.gpr 
> > > gprbuild: unable to find binder driver /opt/sweetada/libexec/gprbuild/gprbind 
> > > make: *** [Makefile:586: kernel_compile_gpr] Error 4 
> > > 
> > > PC-x86-64: start kernel build. 
> > > 
> > > [GPRBUILD-C] build.gpr 
> > > [GPRBUILD-B] build.gpr 
> > > gprbuild: unable to find binder driver /opt/sweetada/libexec/gprbuild/gprbind 
> > > make: *** [Makefile:586: kernel_compile_gpr] Error 4 
> > > 
> > > After this I removed the 1d statements and tried the original 1e menu.sh. 
> > > As before ./menu.sh generated nothing. 
> > > But I individual menu targets worked from all-clean through configure then 
> > > menu.sh all failed with same error: 
> > > 
> > > [RANLIB] libplatform.a 
> > > [GPRBUILD-C] build.gpr 
> > > [GPRBUILD-B] build.gpr 
> > > gprbuild: unable to find binder driver /opt/sweetada/libexec/gprbuild/gprbind 
> > > make: *** [Makefile:586: kernel_compile_gpr] Error 4
> > Ah, sorry, I forget the kernel.cfg problem. 
> > 
> > Are you sure you carry out the right steps? Here a little recap: 
> > 1) 
> > edit menu.sh and choose your target by uncommenting it, leave the others commented 
> > 2) 
> > execute in the shell "./menu.sh all-clean" 
> > 3) 
> > execute in the shell "./menu.sh createkernelcfg" 
> > Some file gets installed, and you should find a proper configured kernel.cfg. Double check. It should replicate your target by means of two variables. 
> > 4) 
> > execute in the shell "./menu.sh configure" 
> > You should get a list of parameters. 
> > 5) 
> > execute in the shell "./menu.sh all" 
> > Compilation of files. 
> > 
> > Let me know if you note something strange.
> 
> I reinstalled 0.1e and now it works, at least to the extent that 0.1d works.
> Quite strange as I had the same problem on both my computers.
> The only thing that I can think of is that on the previous 01e install I just used
> ./menu.sh  ( without target selection)
> which was the method I used for 0.1d. Perhaps this messed something up?
> When that didn't work, I inspected 0.1e menu.sh and discovered the need to use target selection;
> however, on using target selection, in the order stated in your advice (perhaps eventually), I had the reported problem.
> It seems, somehow I messed something up; somehow on both computers!
> Thanks for your much appreciated advice.
> 
> I still haven't tracked down the Catalina problem. Inspiration comes slowly.
> 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.
> Possibly being blocked by Catalina security features?
> I currently don't know how to track outb functionality.
> I'll keep trying (slooowly)

Hi Roger.

Fine, the most important thing is that we have verified that tools run correctly. 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.

Correct me if I'm wrong, I understood that IOEMU window is working and shows I/O widgets cycling, but not in Catalina, is that correct?

In this case maybe there is either a problem in the GUI code or in Catalina handling of windows.

But you can assume safely that Ada code is working since you should see some output in serial terminal.

About the outb instruction, please explain me (even writing down your code) what you are trying to do. outb instructions should behave fine, otherwise you should see a totally dead system.

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 you can change very little in your code. For example, unit x86_64.IO is likely to change in CPU.IO. Ask me if you have difficulties recompiling your code.

Let me know.