A495 porting thread - page 3 - DryOS Development - CHDK Forum supplierdeeply

A495 porting thread

  • 346 Replies
  • 88722 Views
Re: A495 porting thread
« Reply #20 on: 03 / November / 2010, 11:24:22 »
Advertisements
moved
« Last Edit: 03 / November / 2010, 13:53:54 by Dave1116 »
Canon a1100is 100c, sd1200is 100c



Wikipedia - Hack (computer science), an inelegant but effective solution to a computing problem.

*

Online reyalp

  • ******
  • 13436
Re: A495 porting thread
« Reply #21 on: 03 / November / 2010, 18:25:52 »

I have a A490 camera.. I think that they're very similar. I can test it and maybe use your great work for the A490.
No chance that a build for one model will work on a different model.
Don't forget what the H stands for.

Re: A495 porting thread
« Reply #22 on: 03 / November / 2010, 23:52:32 »
Bracketing seem broken. It dos not Ev+/- .

When trying to make a badpixel.bin with the stock badpixel.lua the camera seem to hang.

otherwise looks fine. No crashes.
How about the first beta? can you make a badpixel.bin? Maybe I uploaded a wrong version.

*

pcdude2143

Re: A495 porting thread
« Reply #23 on: 08 / November / 2010, 21:25:41 »
[gone]
« Last Edit: 04 / September / 2017, 14:22:44 by pcdude2143 »


*

Online reyalp

  • ******
  • 13436
Don't forget what the H stands for.

Re: A495 porting thread
« Reply #25 on: 09 / November / 2010, 09:30:30 »
@reyalp

Is it possible that same camera model and firmware can have different PROPSET?
In first beta release, I set CAM_PROPSET to 2 and Johndk reported that everything works fine including scripted shoot button, while in my case, I cannot get badpixel.lua to work and it just hang in shoot() command.

When I set CAM_PROPSET to 3, it seems everything work fine. but...
Quote from: Johndk
Bracketing seem broken. It dos not Ev+/- .

When trying to make a badpixel.bin with the stock badpixel.lua the camera seem to hang.

otherwise looks fine. No crashes.

I don't have the camera right now to test firmware that I uploaded, but I'm pretty sure that I uploaded the right firmware.

@pcdude2143
If you look at my git repository, 100d already there but need more porting. I've done some porting before I got the camera and after I got the camera, dump the firmware, it show 100f... so I just stopped porting 100d camera and don't remember where I stopped. I think boot.c/capt_seq.c/movie_rec.c finished, but need to double check it to make sure and verify that all syntax is correct. I'm not copy-paste and using asmify but write line by line so maybe there's something I missed.

-- edit ---
@reyalp
Is it possible if we just copy bootloader from ROM to RAM and just patch it so we don't need to rewrite everything? I would like to try it but lack of ARM Opcode knowledge especially when calculating (branch/jmp) offset.
« Last Edit: 09 / November / 2010, 09:50:21 by syahmixp »

*

Online reyalp

  • ******
  • 13436
Re: A495 porting thread
« Reply #26 on: 09 / November / 2010, 12:30:45 »
@reyalp

Is it possible that same camera model and firmware can have different PROPSET?
In theory I guess, but in practice I would say no chance. The differences between canon firmware revisions are mostly very minor, frequently only tens to or hundreds of bytes changed.

The newest cameras seem to have new propsets (>3, not currently in the trunk), you might want to look at other ports with the same Dryos revision number.

Quote
Is it possible if we just copy bootloader from ROM to RAM and just patch it so we don't need to rewrite everything? I would like to try it but lack of ARM Opcode knowledge especially when calculating (branch/jmp) offset.
In general, you'd have to relocate it, not just copy it. This isn't impossible, but it's not trivial either. ARM is mostly uses PC relative addressing anyway, so small chunks might work OK with just copying. You would need to deal with jumps into firmware somehow (currently handled by stubs_auto.S) because RAM->ROM is larger than the offset that can be represented by the offset in BL. You might be able to do negative offsets and wrap around, but I'm not sure you can rely on this.
Don't forget what the H stands for.

*

pcdude2143

Re: A495 porting thread
« Reply #27 on: 11 / November / 2010, 09:57:50 »
I tried to load your CHDK just for kicks (downloaded firstbeta to card, activated boot partition), even though the revision is wrong, and I get nothing. The camera boots into normal mode. I've attempted to boot other programs before and the camera froze with the screen off. What am I doing wrong?

Edit: Never mind, I figured it out.
« Last Edit: 11 / November / 2010, 13:44:13 by pcdude2143 »


Re: A495 porting thread
« Reply #28 on: 22 / November / 2010, 18:54:51 »
Hello...

First: My thanks to the developers for their work on CHDK and CardTricks. I use both on my S3IS.

I've bought an a495 (v100F) -- it fits in my pocket, unlike the S3! -- and installed CDHK 0.9.9.9 .  All good. (Thanks syahmi and others)

I'd like to be able to use manual exposure and aperture.

1) Is this possible, and
2) can I place these functions onto the L/R/Up/Dn keys?

Happy to help with testing.

Re: A495 porting thread
« Reply #29 on: 23 / November / 2010, 01:18:21 »
Hello again.

I'm using the 0.9.9 on my a495. It's installed and working well, as best I can see.

The images are being saved correctly as .JPGs, and show up as .CR2s or CRW, as I choose, but neither UFRAW nor the Microsoft RAW Image Viewer (there is one -- ya just have to find it on their site!) will open them.

UFRAW reports "[filename]:Unsupported file format."

Any ideas?

 

Related Topics