The SX1 IS Porting Thread

alexpreyer

As an new SX1 owner I have been also looking on this tread for a while now. It's great that someone has the motivation to do such difficulty things. Unfortunatly I also can only give mental support and offer me as an alpha tester. Thanks for the huge amount of time spending on the porting. I think many people will love you for this.

Alex

fboesch

pev69
Wow, very nice news! I'm a bit puzzled about the screen size, though. Isn't the SX1 supposed to have 230k pixels on the screen, that would indicate something like 640x360 widescreen resolution, so why are those numbers mentioned so small (480x240, 360x240)?

Well, that the SX1 has a "widescreen" is obvious.....but regarding the 230k value: I'm pretty sure that this is the value of Sub-Pixels (R G B = 3 Sub-Pixels for one Pixel). So the effective "User-Resolution" is definately less then 640x360... --> If you compare an HTC Touch Diamond Mobile Screen (effective VGA 640x480) with the SX1 Maindisplay (similar in Size somehow) the density of the Mobile is WORLDS higher than the SX1.

With the 480x240 the CHDK Menü shows up on the whole heigth (nearly full width) in Play Mode. BUT: Depending of the "Custom-Display" Settings (if EV Compensation is shown by the CAM itself) the CHDK Menu will move "up" in Cam-Mode ... the CHDK Menu Header and half of the first menu entry disappear under the upper frame side.

I will mostprobably choose even "thinner" values, so that in all Display Modes of the SX1 the CHDK Menü will show up correctly.

fboesch

Status (after Lunch) 13:15:

CHDK starts up with the DiskBook.bin (Autostart with Locked SD in Play/Mode).

Play Mode can be switched over to Rec-/Cam-Mode.

CHDK works also in Rec-Mode fine (now!).

Menu/OSD works (elements can be re-positioned, menu colors changed)
Zebra works
Histo works
Overlay not correctly (just a bunch of yellow dots show up)

Now what would be interesting: The Extra Photo Settings

The settings can be changed (and are shown as "Changed Settings" during online view. Ok. But if pressing Shutter, the Cam will take the pic and then "die" (Blackscreen, Lens stays out). However: It seems that the Settings (High Shutter Speed or High Aperture) are really working: --> Before the Cam dies, the freshly taken picture will show up for a half second and looks as I would suppose with higher shutter/Aperture --> "Dark")...

Seems that I need investigate further into the part, where the Picture is Captured and processed and then "stored" (I assume capt_seq.c)

Another Trial with invoking CHDK through Pseudo Firmware Update with PS.FI2 File did not work yet...Choosing FW Upgrade (from Canon Menu) will show 2.000 --> 1.1000 but the Cam will die after a second. Reviving it only with opening battery case.

@FE50: Any hint where to check for other things that PS.FI2 Method works on my build?

Cheers

F.

ewavr

fboesch
Any hint where to check for other things that PS.FI2 Method works on my build?

Mmm...
Try to change in tools/packfi2/fi2enc.c in lines 122 - 123:

hdr.unk1=0x02460000; // this value from unpacking official update
hdr.id=0x02010000; // version 2.1.0.0

and maybe in line 127:

fi2rec.addr=0x1900;

edit: If this not helps, please upload your fi2 file.

fboesch

Thanks ewavr!

Tried the suggestions (in two steps). Now "Firm Update" shows nicely 2.0.0.0 --> 2.1.0.0 but still blank (black screen) and dead cam (--> revive with Battery "out")

regarding the Key/IV....as you may have followed: I'm pretty sure that I got them right (not just took them from G10_100F Dump, but also checked within my SX1_200h Dump). They are also in the right order, because I first got them the other way around in fi2.inc ....then the PS.FI2 will show the "file error" (not even showing the confirmation of update 2.0.0.0-->1.1.0.0).

Last Compiled ps.fi2 is here: http://www.zshare.net/download/583094260e64cb7d/

To others: Do not download the file....it is "unsuable" yet...

fboesch

...made some "Proofing" pictures of my SX1 with activated CHDK (pre-alpha) (Pictures shot with my good-old S2IS)

PIC1 - Menu is showing up in "German" and I already customized the colours & fonts

PIC2 - REC-Mode: - As you see: Battery, Memorycard (except Icon?), Zoom value (28mm), Aperture and Iso (real) are showing up correctly, Histogram works good too and even the CCD-Temp (actually CMOS 😀 ....and i took the pictures in "Wide-Picture" mode....Switching between "normal" and "wide" is working with CHDK.

- I've tested the UBasic Script part: Works...and got my lotto numbers for the next game 😉

PIC 3 - And it shows also the small "issue" if one of the Custom-Display-Modes are active: The CHDK Menu will be shifted to the top of +-0 ... The screen is showing the 480x240 setting, with an Arial 18Bold Font.

meddie

Looks great! I can´t wait until the alpha release is ready to download!

pev69

Yes, very good indeed, fboesch, congratulations on the progress 😀

Regarding the display resolution, I also compared for the first time the display to my new Nokia 5800 (640x360), and I cannot believe how coarse the SX1 display now looks :/ It's a stupid thing of Canon to report that the display has "approx. 230000" "dots" in UK, "pixels" in US, Dammit. It must be, as you say, the amount of sub-pixels.

So, that would make the actual pixels to less than 77000, which would put the real res (16:9) to about 368x207, which I actually confirmed to be approx. true with a mm-ruler and magnifying glass (about 6 pix/mm), heh. It has one deviation from normal LCD monitors in that the pixels are aligned like a brick wall, not like a square grid.

ewavr

fboesch
Last Compiled ps.fi2 is here:

All correct in this file, maybe problem is in other code ( in boot.c or loader/sx1/resetcode/main.c or something else).

fboesch

ewavr

fboesch
Last Compiled ps.fi2 is here:

All correct in this file, maybe problem is in other code ( in boot.c or loader/sx1/resetcode/main.c or something else).

Thanks for confirming ps.fi2, ewavr!

I checked again boot.c and found one other value to be corrected....despite using ps.fi2 still doesn't work, now I can start with the diskboot.bin method with the Play AND Power Button (couldn't before...just with Play button pressed for more than 1 sec). Also I do not need to push the Play/Power Button for more than 1 sec as I had to before....

Meanwhile i have also ported movie_rec.c with the adresses of the SX1.

main.c of /loader/sx1/... looks clean to me.

But still dying when taking a picture/movie....But: the override values entered (e.g. 2 sec shutter) do work. The shutter sound and then the shutter opens for the programmed time. But afterwards it seems that when processing/storing should be undertaken there is still a "bug"....the taken pictures are NOT stored on the memory card.

...my guess is it is somewhere in capt_seq.c ...however: For today I do not see it anymore 🙁

fboesch

pev69
Yes, very good indeed, fboesch, congratulations on the progress 😀

Regarding the display resolution, I also compared for the first time the display to my new Nokia 5800 (640x360), and I cannot believe how coarse the SX1 display now looks :/ It's a stupid thing of Canon to report that the display has "approx. 230000" "dots" in UK, "pixels" in US, Dammit. It must be, as you say, the amount of sub-pixels.

So, that would make the actual pixels to less than 77000, which would put the real res (16:9) to about 368x207, which I actually confirmed to be approx. true with a mm-ruler and magnifying glass (about 6 pix/mm), heh. It has one deviation from normal LCD monitors in that the pixels are aligned like a brick wall, not like a square grid.

Thanks for calculating some raw resolution sizes... I will try to use these values (e.g. instead of 480x240 - which perhaps causes the glitch with swapping CHDK upwards) with values of 360x200 (remember: for SX10 it has been set by ewvar to 360x240, which can be, because of the 4:3 display of the SX10)

😀 and thanks to confirm the low-res display in our SX1's *lol* However: They are special displays, also able to work quite well outdoors (sunlight)...perhaps also the special alignment of the pixels... 😀

EDIT: ....tried several builds with values like 360x200 or 480x200 ....none is really good (either scrambled as with 360x240) or at a wrong position (only partly on screen). It seems that my first finding (480x240) is the right one in file "lib.c" for the SX1

reyalp

On the screen resolution:

The bitmap resolution and the live view resolution aren't necessarily the same. On the SD990, the bitmap is 720x240, while the live view (and jpeg playback etc) is the normal 360x240. Canon claims this LCD has " Approx. 230,000 pixels" but it's not clear which this refers to (although really the live view is the important one IMO)

Don't we love marketing 😉

If the SX1 turns out to have this difference, you might find the patches in my sd990 thread helpful.

fboesch

reyalp
If the SX1 turns out to have this difference, you might find the patches in my sd990 thread helpful.

Yes there is a difference: As said: I've tried out compiled versions with 360x200 (physical res?) but then CHDK shows up again completely scrambled... with width set to 480, there are no issues (on the "base" CHDK)....but I will investigate further: As said the overlay feature shows up "scrambled" (yellow dots) overlay similar to the CHDK Menu if using less than 480x240....so eventually the settings in lib.c should be as the SD990 even higher....

Thanks for this hint!

pev69

Some more things about resolution that came to mind:

1) If you aren't too tired, try one more for the screen size parameters: 384x216; don't know about the live-view resolution parameters though
2) Is there any consideration in CHDK for the change between wide/standard aspect ratio? As in SX1 this can be chosen, I just thought it might have some effects that should be considered in CHDK...

fboesch

pev69
1) If you aren't too tired, try one more for the screen size parameters: 384x216; don't know about the live-view resolution parameters though

2) Is there any consideration in CHDK for the change between wide/standard aspect ratio? As in SX1 this can be chosen, I just thought it might have some effects that should be considered in CHDK...

--> Will try, but as seen (on Screenshots) with 480x240 setting it looks good

--> I don't think that it is needed! You can switch between 4:3 and 16:9 format (during "Live-Cam" View) without impacting the CHDK Overlay! (--> I thought too that this could be an issue, but it isn't).
Simply the "black" Side-Frames will show or not....The Size of CHDK is always using the full "width".

P.S. Actually this is very cool....Using the Cam in "normal" 4:3 mode the black side-bars do show the CHDK Information clear and nicely (as seen: I've positioned the additional CHDK Info's to the left or right-side), without to impact the Live-Picture as much as it is on "standard" LCD Displays....

pev69

fboesch
--> Will try, but as seen (on Screenshots) with 480x240 setting it looks good

OK. That just seems so strange, a 2:1 aspect ratio. But if it works, no reason to complain 😀

P.S. Actually this is very cool....Using the Cam in "normal" 4:3 mode the black side-bars do show the CHDK Information clear and nicely (as seen: I've positioned the additional CHDK Info's to the left or right-side), without to impact the Live-Picture as much as it is on "standard" LCD Displays....

My thoughts exactly! It's nice to be able to use extra screen space.

fboesch

....rehi....

It's Saturday, and after first "family stuff" yesterday, I'm back on the "Port"...

Hmm...actually I'm looking for the parameters

CAM_RAW_ROWPIX
CAM_RAW_ROWS

of the SX1...

Interesting the CMOS of the SX1 seems either to have a much larger RAW Pixel size OR there is a change (not Bayer Matrix?) compared to the CCD's used in all other Canon Cams....

Out of FW of the SX1

ROM:FFAFE94C LDR R1, =0x1076D90
ROM:FFAFE950 ADR R0, aCrawBuffSizeP ; "CRAW BUFF SIZE %p"

is enourmous higher value than all other Cams....on the SX10 it is just EC04F0....

And there on the SX110 Porting Thread following arithmetics have been suggested...

0xEC04F0 =15467760
15467760/12*8=10311840
10311840/0,75=13749120
sqrt(13749120)=3708
3708*0,75=2781

However: ewvar used 3720x2772 on his SX10 Port....But does not explain how he came onto these values....

Now regarding the SX1....

0xx1076D90 =17264016
17264016/12*8=11509344
11509344/0,75=15345792
sqrt(15345792)=3917
3917*0,75=2938

3917*2938 (?)

That would be MASSIVELY more than 10MPix.....would point to a kind of 11.5MegaPix Sensor (Well always assuming that it is based on 12bit....)

...And what I think is interesting (out of the SX110 Port): Clearly the CHDK Wiki is missing a understandable Step-by-Step Guide FOR EVERYONE with a basic set of "Programming Language/ASM" Understanding....there are poeple around, but @current stage it is very time consuming, because searching for information in the forum/wiki as well short answers from developers is the time-eater....

PhyrePhoX

yes, it is very time consuming, finding all the neccessary information throughout the forum, and getting all the answers by the "experienced" developers.
this is a problem that is to be found in all projects in which there is no money involved. nobody wants to do the "crap jobs", for example writing a documentation. especially a documentation about porting, which is the hardest job of the dev jobs.
But, in the beginning of the wiki, there virtually was NO documentation, it is getting better gradually, and eventually we will have all the information gathered in a single point of "contact". this needs time, time and committment.
Since it is a wiki, everybody can join in on the fun and edit it. You are more than welcome to help out, especially since you now know what it means to do a port, and you already found all the information that you needed, etc.
i didn't port a cam yet, so i cannot really help here. there aren't a lot of "asm gurus" around here.

fboesch

PhyrePhoX
... You are more than welcome to help out, especially since you now know what it means to do a port, and you already found all the information that you needed, etc.

I think that there are a lot of people around who would like (and would have the skills!) to "port"...but to find the "entry-point" is rather difficult with todays documentation. And without true "step-by-step guide" (plus Screenshots) it is hard - as we all know.

Actually in my eyes, a porter does not need larger developer skills (to start with), but an eye to quickly recognize "pattern" within two codes (one ported - as template - one to be ported). I myself am NOT a developer.

Since I've started it took me about 40hours (nighttime/weekend) and I started on Wednesday two weeks ago....

I really do have the intention to document my "learnings" later. For now I'm just eager to get a "real" Alpha Version to work....

Thank you for you thoughts, PhyrePhox! 😀

ewavr

For SX1 sensor size is 0x1038 * 0xAD4 (see ROM:FFAFE67C for 2.00H and compare it to SX10 1.01A @ ROM:FFAD3764).

So, RAW size = 0x1038 * 0xAD4 * 12 / 8 = 4152*2772*1.5 = 17264016 = 0x1076D90 (as expected)

4152 / 2772 =3 : 2 sensor. Anybody who opened SX1 CR2 file in dcraw, suspected this.

« Previous Page Next Page »