Tag compiler - PPCenter

PPcenter donation system updated !

Written by cafealpha 16 july 2017 4 comments

More than 11 years ago (from winter 2005 ?), I had a "donate" page stating something like "send your money and I will make cool things for Saturn on my free time".

During there 11 years, I received 15 US dollars.

And within theses 15 US dollars, I declined 10 because they were generously donated in exchange of "future help" in making a game for Saturn.

So that's something like 45 cents per year, which is also around 3.8 cents per month. I didn't checked in details, but that should be something like one Skittles per week. Not one bag of Skittles, but one bloody skittles. Per. Week

Fortunately, this era now ends, because I officially announce that I changed my donation system from "send your money and I will make cool things for Saturn on my free time" to "Send everything except money, and I will make cool things for Saturn on my free time. And even if you don't donate anything, I will make cool things for Saturn on my free time anyway."
More details can be found on my donate page

And to make it clear : the motivation to change donation system is not related to money : I just spoke about money received so far in order to write something funny in my blog

I make Saturn things for fun, and not for money. As some examples, I started to design rev2f PCB in hospital room from one week after undergoing cancer surgery, and Virtual Memory Cartridge add-on for Pseudo Saturn Kai was developed and tested during my post surgery chemotherapy. Theses helped a lot to think about something else than medical things during theses times.
I don't say that Kicad and gcc are a cure for cancer (

), but theses were very good help however.

And to make it clearer : yes, I sell Saturn cartridges, but no I don't make a living from selling theses. I'm not even sure I produce enough carts in order to pay every-day's breakfast from cartridges sales benefits

Bit shift in Saturn minimalistic C program

Written by cafealpha 14 june 2017 4 comments

While making a Saturn program running directly from ROM, constraint is usually to have program as small as possible. Why ? Because I would like to make Pseudo Saturn Kai continue supporting Action Replay, which have limited ROM size

So, in that situation, I use homemade, minimalistic stdlib, containing usually only memcpy and memset functions, and everything goes well.
But for some reason, current program was begging for __ashlsi3 and __ashrsi3 functions.
... What's these things ? __ashlsi3 is an assembly function doing left shifts of data, and as you probably guessed, __ashrsi3 does the same, but with right shifts

No problem, let's ask my friend google, and copy & paste theses functions without minding about their contents

Theses functions are standard functions provided by C library, so sources can be found here and there.

An example of what __ashrsi3 function looks like

A day after that, here comes the time to do basic testing of this ROM code

Let's first start with simple things such as screen display ...

Text display ... not as expected ?!

Hrm, it's probably a problem in my printchar routine ?

printchar source code : this is the core thing
behind text display in my programs

But that's a very long time I didn't touched this routine, which works well on Pseudo Saturn Kai, and works even better in vdp1ex from Charles MacDonald sample programs, because all my printchar routines come from there

But just in case of, let's try to tune one " <<3 " into " *8 " in the code above, and see if that changes something. Theses two operations are equivalent, so this should give the same result, but ... Saturn screen becomes all black

Okay, there's definitely something weird regarding that printchar, but I just re-used it as-is from other project, so what's going wrong with my it ?!
[...]
And then (finally) a light-bulb above my head appears

Maybe there's something wrong regarding the __ashlsi3 and __ashrsi3 routines ?
And, yes there was something wrong regarding theses routines ... I wrote a paragraph about them on the first half of this article, so it would be surprising the problem came from somewhere else

In more accurate words, routines are OK, which is normal since they are written by people smarter than me

But the calling convention of __ashrsi3 was not as my gcc was expecting ?
Well, that's just a guess from the display results, because it seems to display the same pixel 8 times on each row of a given character, which may happen when ignoring shift parameter in __ashrsi3 function.

Anyway, rather than finding in details what's wrong, let's fix the problem

First, with assembly by hand, in desperately trying to change input parameter handling ... I don't remember exactly what I wrote, but that was something like pushing a register to stack, moving parameter to it, finally restoring register, putting nop instructions everywhere, etc ... nothing difficult, but over my extent in assembly programming

The result is ... a mixed success :

Trying to modify __ashrsi3 routine by hand ... well, it seems that
some shift values are not correctly handled

Okay, so let's re-ask google about that __ashrsi3 routine ... and a different implementation arrives in search results. Let's try it

__ashrsi3

And the execution result :

Execution result with second version of __ashrsi3 function

Yeah, it works this time !!! And don't ask me why, because I didn't took time in understanding what's different in that second version of __ashrsi3 function

And, rather than understanding why it works ... let's close that assembly pandora box before some other mystic bugs pop from it

I will probably see about this in the future, but that was absolutely out of the scope of today's programming, and in software world, too much digression leads to freeze of projects, which I would like to avoid in order to go forward to next pending project

As a example, I started to adapt yeti3d engine to Saturn in 2010 (7 years ago !), and this ended in ... developing a SD card based memory cartridge for Saturn !

The point above is is not a joke : menus used in my yeti3d adaptation are the origin of menus used in Pseudo Saturn Kai, which shows the continuity (co-consanguinity ?

) in my projects. And after getting yeti3d working a bit, I really would like to load levels from something else than CD-ROM, which was from PC (via adequate link cable) on a first time, and which will (should ?) then evolve to SD card.
That would be cool to make a Saturn game not requiring to burn CD-ROM somedays, but before that I need to finish neighboring side quests

Evolution of my Saturn projects

To conclude this article, let's say it was terribly fun to see some bits of the internals behind C language

By the past, I remember I did something similar with my yeti3d adaptation, but remained at "C language level" : optimization done at that time was (IIRC, ) to avoid 4 bits shifts, because theses are not available in a single SH-2 CPU instruction. Avoiding 4 bits shifts was simply done by merging two fixed point operation in a single one (or something like that : I did this 7 years ago !), and this actually gave some improvements in 3D scene rendering

Theses were the good times ... I sometimes think "I'm Getting Too Old For This Shit", but that's only to motivate to finish my old projects

But before that, Pseudo Saturn Kai, and then Kicad and Quartus are waiting for me

BTW, in the case you wondered about what was today's programming session, you probably guessed it was about exception handler addition to Pseudo Saturn Kai. This not a new feature, since it was available in Pseudo Saturn 0.83x ... in fact, I grabbed some sources from Pseudo Saturn 0.83x in order to implement this exception handler (thank you CyberWarriorX !)

This exception handler will be available as a small add-don to cheat codes feature in Pseudo Saturn Kai next major release.

Gamer's Cartridge out of stock :]

Written by cafealpha 15 february 2017 5 comments

Out of stock ":]". I'm glad to have finished this batch

I don't plan to sell Gamer's Cartridge for a while, because stock of parts to build theses cartridges (electronics components, PCBs, labels, etc) is currently very low here. I'm even lacking of bubble paper used when shipping cartridges

So, what's next ? Of course, Saturn stuff

I plan to use this "break" in cartridges manufacturing and sales in order to continue Pseudo Saturn Kai development.
Main feature to add is cheat codes, which is a bit "heavy" one to implement, because processing in order to make cheat codes working isn't documented in details.
But that will be done ! Also, there are some side quests here and there regarding Pseudo Saturn Kai features. I plan to implement as far I can, so it will be limited only by my free time, my motivation, and flash ROM remaining on cartridge

data/images/20170215_sgc_v33b_gerber_preview.tb.png

Gerber preview before ordering PCB on
Seeed Studio, very classy and realistic

Edit (2017/05/11) : finally back in stock

I catched the occasion to make some minor improvements to my homepage, such as adding anchor link to some sections, adding some directions for Japanese users, etc ... and I'm already full up with writing HTML

Edit (2017/05/12) : half of the stock already reserved oO

data/images/20170512_escalated_quickly.jpg

Cartridges are assembled by hand, hence stock is small, but I'm impressed anyway

New compiler for my Saturn stuff !

Written by cafealpha 05 august 2014 no comments

Today, I just changed all my projects configuration and sources in order to use latest "Saturn SDK" compilers

Very boring work, but now I feel happy to get all my projects updated !

Motivation hedgehog for today work, and future work too :

Here is a list of problems I fixed to get the new compilers working :
- Don't call directly ld, instead call gcc -o. Why ? because ld can't find properly path to libgcc.a ...
- Consequently, some link parameters need to be changed :
    "--script bart.lnk" → "-T bart.lnk"
    "-Map main_elf.map" → "-Wl,-Map=main_elf.map"
- Some signed/unsigned mess that need to be fixed ... old compiler was quiet about this, which made me not worrying about data signedness ^^;
- Removed volatile keyword in function declaration ... it actually didn't made sense to use volatile elsewhere than in data declaration !
    /* Exit to multiplayer. */
    //(**(volatile void(**)(void))0x600026C)();
    (**(void(**)(void))0x600026C)();
- Removed SBL sources that were used to read file from CDROM, because they don't compile properly except in -O0 (non) optimisation mode ... Instead, I use source from great CyberWarriorX library

PPCenter :: devblog

PPcenter. Arts and craft for my Sega Saturn. Since 1847 !

PPcenter donation system updated !

Bit shift in Saturn minimalistic C program

Gamer's Cartridge out of stock :]

New compiler for my Saturn stuff !