s80 anybody? - page 20 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 ... 15 16 17 18 19 [20] 21   Go Down

s80 anybody?

  • 203 Replies
  • 61117 Views
*

Offline powershots80

  • *
  • 26
Re: s80 anybody?
« Reply #190 on: 05 / August / 2013, 03:04:25 »
Advertisements
Release 1.2.0 version works fine too. 
Thanks for your update!

Noticed the manual flash indicator is no longer showing via OSD but I can live without it.
Menus are a little different but seems more organized.

Charlie
Logged
*

Offline brzh29

  • *
  • 2
Re: s80 anybody?
« Reply #191 on: 17 / November / 2013, 17:12:26 »
Hi all,

Sorry to move this old topic up. Actually, I have just got one S80 camera and I searched how I can use the RAW format, so I found CHDK and this forum.
My problem is that I cannot use the CHDK firmware for the S80 as the firmware in the camera is the 1.00F version. It seems that the 1.00G is required to get extra-functions.

I cannot find the 1.00G version anywhere (links are all dead), and if someone can help me with this, this would be great.

Many thanks.

Logged
*

Offline srsa_4c

  • ******
  • 4031
Re: s80 anybody?
« Reply #192 on: 17 / November / 2013, 17:29:43 »
Quote from: brzh29 on 17 / November / 2013, 17:12:26
I cannot find the 1.00G version anywhere (links are all dead), and if someone can help me with this, this would be great.
Here's the link (beware, heavily ad-infested site, try with ad-blocking) http://www.sendspace.com/file/og0hri
You can verify it with the signatures found on the s80 wikia page: http://chdk.wikia.com/wiki/S80
Logged
*

Offline brzh29

  • *
  • 2
Re: s80 anybody?
« Reply #193 on: 18 / November / 2013, 06:58:16 »
Hello,

Thanks a lot for the link. Just downloaded the file. Checked the MD5, it's OK.

Now have to install it in the camera and then try CHDK and raw format... I will do this soon and will come back if something goes wrong.

Regards
Logged
*

Offline reyalp

  • ******
  • 12159
Re: s80 anybody?
« Reply #194 on: 09 / June / 2018, 17:28:07 »
@koshy posted a dump for S80 firmware 101b here: https://chdk.setepontos.com/index.php?topic=13450.0

sig finder shows many addresses changed, so this will need a new sub port.
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 979
Re: s80 anybody?
« Reply #195 on: 09 / June / 2018, 17:42:22 »
Quote from: reyalp on 09 / June / 2018, 17:28:07
@koshy posted a dump for S80 firmware 101b here: https://chdk.setepontos.com/index.php?topic=13450.0
sig finder shows many addresses changed, so this will need a new sub port.

This is a little weird, but I intended to attack this one on my own.
I know I said before that I wouldn't do this kind of thing. Well, little did I know.

If I need help I'll post here.
Logged
*

Offline reyalp

  • ******
  • 12159
Re: s80 anybody?
« Reply #196 on: 09 / June / 2018, 17:58:46 »
Quote from: koshy on 09 / June / 2018, 17:42:22
This is a little weird, but I intended to attack this one on my own.
I know I said before that I wouldn't do this kind of thing. Well, little did I know.

If I need help I'll post here.
Porting a new "sub" isn't super difficult. Some slightly out of date advice can be found at http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version

The part that's out of date is that code_gen is a much better (in terms of accuracy and future maintainability) way to generate the inline assembler. Unfortunately for you, the original s80 port wasn't done with code_gen, so to use that approach, you'll have to do the code_gen conversion from scratch.

This is an old vxworks camera, so there aren't many (any?) examples of full code_gen ports, but a few like ixus55_sd450 and ixus750_sd550 it for capt_seq and filewrite.
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 979
Re: s80 anybody?
« Reply #197 on: 09 / June / 2018, 18:05:42 »
Quote from: reyalp on 09 / June / 2018, 17:58:46
Unfortunately for you, the original s80 port wasn't done with code_gen, so to use that approach, you'll have to do the code_gen conversion from scratch.
Yes discovered that already. Coding archaeology with CHDK-PT. Great thing it turns out.
I have one question I guess. The S80 100G port's boot method:

Code: [Select]
void boot()
{

    long *canon_data_src = (void*)0xFFB1A3F0; //
    long *canon_data_dst = (void*)0x1900; //
    long canon_data_len = 0xefe0; //
    long *canon_bss_start = (void*)0x108E0; // just after data
    long canon_bss_len = 0xA27F0 - 0x108E0; //
    long i;

    asm volatile ( // loc_FF8100E0
"MRC     p15, 0, R0,c1,c0\n"
"ORR     R0, R0, #0x1000\n"
"ORR     R0, R0, #4\n"
"ORR     R0, R0, #1\n"
"MCR     p15, 0, R0,c1,c0\n"
    :::"r0");

    for(i=0;i<canon_data_len/4;i++)
canon_data_dst[i]=canon_data_src[i];

    for(i=0;i<canon_bss_len/4;i++)
canon_bss_start[i]=0;

    asm volatile ( // loc_FF81015C
"MRC     p15, 0, R0,c1,c0\n"
"ORR     R0, R0, #0x1000\n"
"BIC     R0, R0, #4\n"
"ORR     R0, R0, #1\n"
"MCR     p15, 0, R0,c1,c0\n"
"LDR LR, [SP],#4\n"
    :::"r0");

    h_usrInit();
}
Do I need to adjust this one? I think I should have all others under controll by now just need to follow through on them.
Logged
*

Offline reyalp

  • ******
  • 12159
Re: s80 anybody?
« Reply #198 on: 09 / June / 2018, 18:21:32 »
Quote from: koshy on 09 / June / 2018, 18:05:42
Do I need to adjust this one? I think I should have all others under controll by now just need to follow through on them.
The canon_data_src, canon_bss_start and canon_bss_len may have changed. Nothing else in the quoted code should have changed.
The bss start is the end of RAM data noted in stubs_entry.S, and MEMISOSTART defines the length.
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 979
Re: s80 anybody?
« Reply #199 on: 09 / June / 2018, 18:44:58 »
Quote from: reyalp on 09 / June / 2018, 18:21:32
Quote from: koshy on 09 / June / 2018, 18:05:42
Do I need to adjust this one? I think I should have all others under controll by now just need to follow through on them.
The canon_data_src, canon_bss_start and canon_bss_len may have changed. Nothing else in the quoted code should have changed.
The bss start is the end of RAM data noted in stubs_entry.S, and MEMISOSTART defines the length.
Thanks. I'l look at it.
Logged
Pages: 1 ... 15 16 17 18 19 [20] 21   Go Up
« previous next »
 

Related Topics