@RossH Thanks for keeping Catalina going. It's nice to have options...
I just installed the latest version to see if it could run this MicroMax Chess code...
It compiles and run, but just like FlexC, it hangs if you hit enter when it is supposed to look for a move.
You can manually move pieces by entering moves like "e2e4", but also just like FlexC, there is something wrong with the black pawns... They don't move, for example.
Anyway, don't expect you to do anything about it, just letting you know I'm testing out Catalina.
This code was designed to use as few a characters as possible, which seems very silly to me... I imagine why that is why compilers might have a hard time with it...
This chess code seems to work, except that the function GetMillisecs() needs fixing because I hacked it to make it compile.
The interface asks how many seconds to give computer. If you say "0", it moves right away. If you say "1", it thinks longer that I could wait for...
Also, it can't find the opening book file even though I put it on the uSD card of the Eval board...
@RossH Thanks for keeping Catalina going. It's nice to have options...
I just installed the latest version to see if it could run this MicroMax Chess code...
It compiles and run, but just like FlexC, it hangs if you hit enter when it is supposed to look for a move.
You can manually move pieces by entering moves like "e2e4", but also just like FlexC, there is something wrong with the black pawns... They don't move, for example.
Anyway, don't expect you to do anything about it, just letting you know I'm testing out Catalina.
This code was designed to use as few a characters as possible, which seems very silly to me... I imagine why that is why compilers might have a hard time with it...
Seems to work ok for me. But I must admit I only played a few moves, because each move takes a looooonnnnnggg time!
What are you running it on, and what command did you use? I ran it on a P2, and used the command:
This chess code seems to work, except that the function GetMillisecs() needs fixing because I hacked it to make it compile.
The interface asks how many seconds to give computer. If you say "0", it moves right away. If you say "1", it thinks longer that I could wait for...
Also, it can't find the opening book file even though I put it on the uSD card of the Eval board...
I was interested as to why the MicroMax chess program is so slow, so I did some measurements on it. I only did a couple of runs, but the reason becomes clear almost immediately - most of the work is done by one function (D), which is recursive. This very complex function gets called anywhere between 200,000 and 500,000 times while searching for the best move, and it recurses to a depth of 25 or so calls.
I think the author was concentrating on program size, not speed!
@RossH i think you are right. Although it seems to have been ported to microcontrollers. The code is very obtuse though. I think I like the look of ngplay better.
I tried out MicroMax again after seeing it in Gameduino...
This code seems to work with Catalina. Rigged for computer vs computer.
Had to bypass the millis() function though.
In FlexProp, there is now _getms().
Not sure this is really used by the chess engine itself, so I didn't bother to fix it.
BTW: Is there a way to escape from the payload terminal and get back to command line?
It does still build a chess program I tried before with Catalina, NGplay_61.c, so that's good.
Tried to compile lvgl (https://github.com/lvgl/lvgl), but it's not finding the include files...
There are about a thousand include files...
Catalina does not seem to be finding them.
I'm sure I'm doing something wrong...
This is asking a lot, but if you want to see what I'm looking at...
The build.bat file in the attached tries to compile lvgl_test1.c
It looks like it finds include files in the current directory, but not in the \src directory tree...
Tried to compile lvgl (https://github.com/lvgl/lvgl), but it's not finding the include files...
There are about a thousand include files...
Catalina does not seem to be finding them.
I'm sure I'm doing something wrong...
There is something wrong with your directory structure. Here is first error message I get, with an example of the problem:
cpp: ./lv_conf_internal.h:41 ./src/misc/lv_log.h:16 ./lvgl.h:25 lvgl_test1.c:3 Could not find include file "../../lv_conf.h"
So, decoding that:
lvgl_test1.c includes ./lvgl.h at line 3 ./lvgl.h includes ./src/misc/lv_log.h at line 25 ./src/misc/lv_log.h includes ./lv_conf_internal.h at line 16 ./lv_conf_internal.h includes ../../lv_conf.h at line 41
But from the location you are compiling lvgl_test1.c there is no ../../lv_conf.h - however, there is one at ./lv_conf.h
I have updated payload to allow it to be used to program FLASH RAM on the P2 without needing to reset the microswitches on the P2_EVAL board. This required a modification to the Propeller version detection code (basically, you can now override it and manually specify your Propeller version). This update allows payload to correctly use the 100ms serial window on the Propeller 2.
Attached is a zip file containing the new version of payload and the updated README_P2.TXT file. This version will be included in Catalina 4.7 when I have finished testing the current beta release. Here is an extract from the updated README_P2.TXT file:
There is also a a payload-based utility that can program the FLASH RAM on the
P2_EVAL board:
flash_payload program.bin [ other payload options ]
e.g:
flash_payload othello.bin -b230400 -z -i
Note that you must have the microswitches on the P2_EVAL PCB set correctly to
program the FLASH. Here is one way to do it:
FLASH set to ON
P59^ set to ON
P59v set to OFF
Then, execute the flash_payload command, and once all the LEDs have gone out
(which indicates the FLASH programming has completed) set the P59^ microswitch
to OFF and reset the P2 to execute the loaded program from FLASH.
Another way to do this is possible, which does not require microswitch changes.
However, this method only works if you override payload's normal autodection
of whether it is talking to a Propeller 1 or a Propeller 2 using the -o option.
Set the microswitches as follows:
FLASH set to ON
P59^ set to OFF
P59v set to OFF
Now, by executing the flash_payload command with the -o2 option, you can load
the FLASH RAM and then execute the program from FLASH in one command without
needing to change any of the microswiches. For example:
I have just uploaded a validated (i.e. non-beta) release of Catalina 4.7 to sourceforge. This release is for both Linux and Windows. There are a few changes from the beta release:
NATIVE is now the default mode for the Propeller 2.
there is a new version of the payload loader, with improved support for FLASH RAM on the Propeller 2.
Code::Blocks is no longer supported on Linux (it remains supported on Windows).
See the first post in this thread for more details.
I've just uploaded Catalina 4.8 to Sourceforge. There aren't many differences to 4.7, so I've also uploaded some small "patch" files to the errata directory (https://sourceforge.net/projects/catalina-c/files/errata/) which you can use to upgrade an existing 4.7 release to 4.8 without having to download and install the whole new release.
The differences are very minor (mostly some missing documentation updates and an update to the inline PASM function).
Here is an extract from the README.TXT:
RELEASE 4.8
Updates to the reference manuals and the command summaries to include the
changes made to payload in release 4.7.
A bug introduced in release 4.7 when making NATIVE the default memory
model on the P2 has been fixed.
The definition of the PASM() function (used to include inline PASM in C
code) has been modified to indicate it can return an int rather than a void.
This prevents Catalina from overwriting return values (i.e. the value
present in r0 when the PASM code finishes execution). The new definition is:
extern int PASM(const char *code);
This should not make any difference to existing code that does not use the
return value of the PASM function. New PASM example program called
test_inline_pasm_3.c and test_inline_pasm_4.c have been added to the
examples in the demos\spinc folder to illustrate the use of the return value.
Updated the build_all scripts in the demos\spinc folder to only build demo
programs appropriate to the propeller type (i.e. 1 or 2).
The file flash_led.obj was missing from the demos\spinc folder.
The bug mentioned in point 2 was very minor and is unlikely to have affected anyone's C programs except mine (the compiler was defining both __CATALINA_NATIVE and __CATALINA_TINY in some cases when it should have defined just __CATALINA_NATIVE).
I have no plans for another release of Catalina just yet, but I have a question ...
I recently dropped support for the Code::Blocks IDE under Linux (I can no longer get it to compile), and I expect to do so in Windows soon (same reason - it is becoming almost impossible to compile). Also, Code::Blocks is far too complex for the type of projects we typically build on the Propeller.
The Catalina Geany IDE (which will remain supported) is much simpler and easier to use.
However, one advantage Code:Blocks did have is that you didn't have to have a make utility installed - it has an equivalent built in. Geany does not have this - it can build simple projects very easily, but complex projects must use an external Makefile, and therefore (on Windows) this requires you to also install a version of make.
So ... here is the question ...
Would it be ok to assume Windows users can install and use a version of make (e.g. from http://gnuwin32.sourceforge.net/packages/make.htm) to build all the example programs and demos? Doing so would mean that I would no longer have to support different batch scripts on Windows and Linux - I could just use a common Makefile.
Obviously, I am thinking 'yes' because it would save me quite a lot of work - but I am interested in hearing other opinions before I finally decide.
Rossh
P.S. Also, just an early warning - the next version of Catalina will probably remove the -F compiler option, which allowed the binary output to be produced in different formats (e.g. Motorola S record or Intel Hex format). You will of course still be able to generate the standard Parallax formats - .bin on the P2, or .binary or .eeprom on the P1. If anyone still needs this capability (I can't even remember now who originally requested it) then the srecord utility (which is what -F invokes) has a stand-alone version you can use to do the same job. It no longer seems necessary to have this capability embedded within Catalina. Again, comments welcome.
Would CodeLite be a replacement worth looking at? I think it's a maintained fork of Code::Blocks. Otherwise, is there any accessible/reusable portion of LccWin32?
@Circuitsoft said:
Would CodeLite be a replacement worth looking at? I think it's a maintained fork of Code::Blocks. Otherwise, is there any accessible/reusable portion of LccWin32?
Sorry, just saw this - been busy. I think CodeLite would have the same compilation nightmares as Code::Blocks, since it also uses wxWidgets (which was Code::Blocks downfall).
Geany does everything I need, is much simpler to modify, build and use, so I have decided to go with that. The only thing missing from Geany on Windows was the lack of a built-in ability to build complex programs (which Code::Blocks had). But since I have now added **make **to do that particular task, this deficiency has been very neatly solved.
I have just released Catalina 4.9. See the first post in this thread for details. It is primarily a Propeller 1 "bug fix" release, but it also adds better integration between Catalina, Geany and make on the Propeller 2.
I would appreciate feedback on the installation process from Windows users. I have seen some odd initial behavior - basically, on initial install some programs (most notably Geany) seem to crash or not run at all ... then, a few minutes later, everything seems to work fine without further intervention. I am presuming this is some weird new Windows 10 behavior, but every time I try and reproduce it, it just seems to go away by itself before I can figure out what's wrong.
Errata file deleted, as it would cause problems with release 4.9.1. It is still available on SourceForge for 4.9 users - but better to upgrade to 4.9.1.
@RossH Just download and installed on a relatively old computer running Win10 that didn't have Catalina before.
The install went as expected. Having trouble with Geany though...
The file->Open command takes a very long time to bring up the file browser, but eventually does.
When I try to open the star trek game example, startrek.c, it crashes.
Rebooted, but it still does this.
Thanks, Rayman. My problem is that on every computer I have installed it, it ends up working after a while ... but I'm not sure how or why.
One thing to try - it doesn't seem to like being opened from the Start Menu straight after the install. Can you try opening a Catalina Command Line window and start geany from that using the command "catalina_geany"? It seems that once it has run successfully once, it runs ok thereafter no matter how it is started. Also, if you get it to run once, go into the Edit->Preferences menu, and on the Miscellaneous tab, select both the Project Options - i.e.:
"Use project-based session files"
"Store project files inside the projects base directory"
I'll investigate further now that I know it is not just my imagination!
RossH
Posts: 4,908
Comments
I just installed the latest version to see if it could run this MicroMax Chess code...
It compiles and run, but just like FlexC, it hangs if you hit enter when it is supposed to look for a move.
You can manually move pieces by entering moves like "e2e4", but also just like FlexC, there is something wrong with the black pawns... They don't move, for example.
Anyway, don't expect you to do anything about it, just letting you know I'm testing out Catalina.
This code was designed to use as few a characters as possible, which seems very silly to me... I imagine why that is why compilers might have a hard time with it...
The interface asks how many seconds to give computer. If you say "0", it moves right away. If you say "1", it thinks longer that I could wait for...
Also, it can't find the opening book file even though I put it on the uSD card of the Eval board...
I did the compile and load like this:
Seems to work ok for me. But I must admit I only played a few moves, because each move takes a looooonnnnnggg time!
What are you running it on, and what command did you use? I ran it on a P2, and used the command:
I haven't looked at the code, but to use the SD Card you need to use -lcx instead of -lc
I was interested as to why the MicroMax chess program is so slow, so I did some measurements on it. I only did a couple of runs, but the reason becomes clear almost immediately - most of the work is done by one function (D), which is recursive. This very complex function gets called anywhere between 200,000 and 500,000 times while searching for the best move, and it recurses to a depth of 25 or so calls.
I think the author was concentrating on program size, not speed!
Ross.
This code seems to work with Catalina. Rigged for computer vs computer.
Had to bypass the millis() function though.
In FlexProp, there is now _getms().
Not sure this is really used by the chess engine itself, so I didn't bother to fix it.
BTW: Is there a way to escape from the payload terminal and get back to command line?
CTRL-D
Catalina 4.7 has been released (currently, Windows only). See the first post in this thread for details.
Just installed... Windows complained a lot, but was able to get it to install.
Seem to be missing the "Catalina Command Line" shortcut in the start menu. But, I found it in the install folder.
It does still build a chess program I tried before with Catalina, NGplay_61.c, so that's good.
Tried to compile lvgl (https://github.com/lvgl/lvgl), but it's not finding the include files...
There are about a thousand include files...
Catalina does not seem to be finding them.
I'm sure I'm doing something wrong...
This is asking a lot, but if you want to see what I'm looking at...
The build.bat file in the attached tries to compile lvgl_test1.c
It looks like it finds include files in the current directory, but not in the \src directory tree...
Hi Rayman
Will have a look tomorrow.
rossh
There is something wrong with your directory structure. Here is first error message I get, with an example of the problem:
So, decoding that:
lvgl_test1.c includes ./lvgl.h at line 3
./lvgl.h includes ./src/misc/lv_log.h at line 25
./src/misc/lv_log.h includes ./lv_conf_internal.h at line 16
./lv_conf_internal.h includes ../../lv_conf.h at line 41
But from the location you are compiling lvgl_test1.c there is no ../../lv_conf.h - however, there is one at ./lv_conf.h
rossh
Odd. Works ok for me. What version of Windows are you using?
rossh
Latest Win10. I still had the last version installed though. Maybe that messed it up somehow…
Thanks for looking at the code issue. Looks like an easy fix.
I have updated payload to allow it to be used to program FLASH RAM on the P2 without needing to reset the microswitches on the P2_EVAL board. This required a modification to the Propeller version detection code (basically, you can now override it and manually specify your Propeller version). This update allows payload to correctly use the 100ms serial window on the Propeller 2.
Attached is a zip file containing the new version of payload and the updated README_P2.TXT file. This version will be included in Catalina 4.7 when I have finished testing the current beta release. Here is an extract from the updated README_P2.TXT file:
rossh
I have just uploaded a validated (i.e. non-beta) release of Catalina 4.7 to sourceforge. This release is for both Linux and Windows. There are a few changes from the beta release:
See the first post in this thread for more details.
rossh
I've just uploaded Catalina 4.8 to Sourceforge. There aren't many differences to 4.7, so I've also uploaded some small "patch" files to the errata directory (https://sourceforge.net/projects/catalina-c/files/errata/) which you can use to upgrade an existing 4.7 release to 4.8 without having to download and install the whole new release.
The differences are very minor (mostly some missing documentation updates and an update to the inline PASM function).
Here is an extract from the README.TXT:
The bug mentioned in point 2 was very minor and is unlikely to have affected anyone's C programs except mine (the compiler was defining both __CATALINA_NATIVE and __CATALINA_TINY in some cases when it should have defined just __CATALINA_NATIVE).
Ross.
I have no plans for another release of Catalina just yet, but I have a question ...
I recently dropped support for the Code::Blocks IDE under Linux (I can no longer get it to compile), and I expect to do so in Windows soon (same reason - it is becoming almost impossible to compile). Also, Code::Blocks is far too complex for the type of projects we typically build on the Propeller.
The Catalina Geany IDE (which will remain supported) is much simpler and easier to use.
However, one advantage Code:Blocks did have is that you didn't have to have a make utility installed - it has an equivalent built in. Geany does not have this - it can build simple projects very easily, but complex projects must use an external Makefile, and therefore (on Windows) this requires you to also install a version of make.
So ... here is the question ...
Would it be ok to assume Windows users can install and use a version of make (e.g. from http://gnuwin32.sourceforge.net/packages/make.htm) to build all the example programs and demos? Doing so would mean that I would no longer have to support different batch scripts on Windows and Linux - I could just use a common Makefile.
Obviously, I am thinking 'yes' because it would save me quite a lot of work - but I am interested in hearing other opinions before I finally decide.
Rossh
P.S. Also, just an early warning - the next version of Catalina will probably remove the -F compiler option, which allowed the binary output to be produced in different formats (e.g. Motorola S record or Intel Hex format). You will of course still be able to generate the standard Parallax formats - .bin on the P2, or .binary or .eeprom on the P1. If anyone still needs this capability (I can't even remember now who originally requested it) then the srecord utility (which is what -F invokes) has a stand-alone version you can use to do the same job. It no longer seems necessary to have this capability embedded within Catalina. Again, comments welcome.
Ross.
Would CodeLite be a replacement worth looking at? I think it's a maintained fork of Code::Blocks. Otherwise, is there any accessible/reusable portion of LccWin32?
Sorry, just saw this - been busy. I think CodeLite would have the same compilation nightmares as Code::Blocks, since it also uses wxWidgets (which was Code::Blocks downfall).
Geany does everything I need, is much simpler to modify, build and use, so I have decided to go with that. The only thing missing from Geany on Windows was the lack of a built-in ability to build complex programs (which Code::Blocks had). But since I have now added **make **to do that particular task, this deficiency has been very neatly solved.
Ross.
All
I have just released Catalina 4.9. See the first post in this thread for details. It is primarily a Propeller 1 "bug fix" release, but it also adds better integration between Catalina, Geany and make on the Propeller 2.
I would appreciate feedback on the installation process from Windows users. I have seen some odd initial behavior - basically, on initial install some programs (most notably Geany) seem to crash or not run at all ... then, a few minutes later, everything seems to work fine without further intervention. I am presuming this is some weird new Windows 10 behavior, but every time I try and reproduce it, it just seems to go away by itself before I can figure out what's wrong.
Ross.
Errata file deleted, as it would cause problems with release 4.9.1. It is still available on SourceForge for 4.9 users - but better to upgrade to 4.9.1.
@RossH Just download and installed on a relatively old computer running Win10 that didn't have Catalina before.
The install went as expected. Having trouble with Geany though...
The file->Open command takes a very long time to bring up the file browser, but eventually does.
When I try to open the star trek game example, startrek.c, it crashes.
Rebooted, but it still does this.
Tried on a better Win10 computer after uninstalling Catalina 3.15.4.
Same thing.
Well, the file-Open was lightning fast. But, it crashed after opening startrek.c.
It shows the code for about 3 seconds then crashes with no user input.
Thanks, Rayman. My problem is that on every computer I have installed it, it ends up working after a while ... but I'm not sure how or why.
One thing to try - it doesn't seem to like being opened from the Start Menu straight after the install. Can you try opening a Catalina Command Line window and start geany from that using the command "catalina_geany"? It seems that once it has run successfully once, it runs ok thereafter no matter how it is started. Also, if you get it to run once, go into the Edit->Preferences menu, and on the Miscellaneous tab, select both the Project Options - i.e.:
I'll investigate further now that I know it is not just my imagination!
Ross.
@RossH Tried that, but it still crashes a couple seconds after loading...