IXUS 1000 HS Porting Thread

  • 418 Replies
  • 49489 Views
Re: IXUS 1000 HS Porting Thread
« Reply #60 on: 31 / October / 2010, 13:08:01 »
Advertisements
I want upload, but dropio seem not work,

http://blog.drop.io/2010/10/29/an-important-update-on-the-future-of-drop-io/

zshare work once not, but after a second try after 10 minutes, i can upload.here is link to the sourcefile i use.i think i have nothing deactivate, i have only activate some V3 code in V4.

http://www.zshare.net/download/8219346288d77d91/
Ixus 1000 HS

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #61 on: 31 / October / 2010, 13:12:18 »
yes dropio is dying out

I get your boot.c

Re: IXUS 1000 HS Porting Thread
« Reply #62 on: 31 / October / 2010, 13:21:21 »
I forget to answer your Question

>do you see the chdk logo ?

no a chdk logo i see not.I see only that many hooks are deactivate by default und also the "BL sub_FF83D2AC\n"

was deactivate on the V4.

when i do Firmware update, i get the normal image display of old firmware, but after 4-5 sec the LED light short on, and camera switch off.

camera not crash, because when i press play button camera switch on.but after that camera do not switch off automatic after 5 sec
Ixus 1000 HS

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #63 on: 31 / October / 2010, 13:22:41 »
do you trace any error past this line
 //             "BL sub_FF83D2AC\n" // start diskboot.bin


test v5 from here, I disabled the //"      LDR   R3, =mykbd_task \n"            // PhySw Task patch

http://www.4shared.com/file/QDdEZA6M/bootcixus1000v005.html
« Last Edit: 31 / October / 2010, 13:37:03 by asm1989 »


Re: IXUS 1000 HS Porting Thread
« Reply #64 on: 31 / October / 2010, 13:45:40 »
>do you trace any error past this line
> //             "BL sub_FF83D2AC\n" // start diskboot.bin

This was test with my modified V4, i test soon with your V5 and let you know.

I have add before this line a BL blink.No error come and the LED blink.
But when i remove the BL blink, i get that romlog error now.seem this error happen after 4-5 sec.

Exception!! Vector 0x10
Occured Time  2010:10:31 18:40:06
Task ID: 17039396
Task name: SpyTask
Exc Registers:
0xE667FDE8
0xE59FF014
0x0038E234
0x0038E1A0
0x001801DB
0x0018A958
0x00000002
0x00000001
0x19980218
0x19980218
0x19980218
0x0038E19C
0x0038E1A0
0x0038E1A8
0xFF836DBC
0x001BA9F8
0x60000013
StackDump:
0x00000000
0x00372C5C
0x0018E7F8
0x00372C0C
0x0038E1F8
0x00000001
0x000002E4
0x000000C6
0x00000001
0x19980218
0x0017B9AB
0x0017BBD1
0x00000191
0x19980218
0x0017BC91
0x19980218
0x00000001
0xFF8128AC
0x00000032
0xFF83B5B8
0x00000000
0x02FAF080
0x00000191
0x00000191
0x19980218
0x00000001
0x19980218
0x00172D31
0x00372C0C
0x19980218
0x19980218
0x0018EC3C
0x19980218
0x0038E238
0xFF816B74
0x0018EC3C
0x19980218
0x19980218
0x00001008
00000150: *** Camera Log Start ***

00000210: UI:LogicalEvent:0x5001:adr:0,Para:0

00000210: SS:S-Imag

00000230: UI:ScreenLock

00000230: UI:ScreenUnLock

00000230: UI:LogicalEvent:0x300a:adr:0,Para:0

00000230: UI:HDMIConnectCnt

00000230: UI:PB.Create

00000250: UI:LogicalEvent:0x301c:adr:0,Para:0

00000280: UI:PB.CreateE

00000280: UI:DisplayPhysicalScreenCBR

00000280: UI:DispSwCon_TurnOnBackLight

00000280: UI:TurnOnBackLight

00000350: UI:MuteOffPhysicalScreen

00000350: UI:LogicalEvent:0x3138:adr:0,Para:0

00000440: UI:LogicalEvent:0x5006:adr:0,Para:0

00000440: UI:AC:StartPB

00000440: UI:DispSwCon_TurnOnDisplayDevice

00000440: UI:AC:EBtn

00000440: UI:PB.Start

00000440: UI:DSIC:47,0

00000470: UI:CC_CompFlhJpg

00000470: UI:_CompFlhJpg

00000470: UI:PB.Flash

00000470: UI:ScreenLock

00000470: UI:DSIC:47,0

00000470: UI:ScreenUnLock

00000480: UI:ScreenLock

00000480: UI:DSIC:47,0

00000480: UI:LogicalEvent:0x3209:adr:0x12,Para:18

00000550: UI:LogicalEvent:0x301c:adr:0x5a,Para:90

00000650: UI:PB.DrawI

00000680: UI:PB.StartE

00000680: UI:DisplayPhysicalScreenCBR

00000680: UI:PB.TOTAL

00000680: UI:LogicalEvent:0x320a:adr:0,Para:0

00000690: UI:PB.DPOF

00000740: UI:LogicalEvent:0x321f:adr:0,Para:0

00000740: UI:PB.CTG

00000770: UI:LogicalEvent:0x3203:adr:0,Para:0

00000780: UI:PB.DcdCBR

00000780: UI:DSIC:48,0

00000780: UI:PB.RfrsI

00000800: UI:LogicalEvent:0x3201:adr:0,Para:0

00000800: UI:ScreenUnLock

00000810: UI:DSIC:48,0

00000820: UI:PB.DrawI

00000860: UI:ScreenLock

00000870: UI:PB.RfrsI

00000880: UI:ScreenUnLock

00000890: UI:DSIC:48,0

00000900: UI:DispSw: Unlock

00000900: UI:DispSwCon:Unlock

00000900: UI:DispSwCon_TurnOnBackLight

00000900: UI:DispSwCon_MuteOffPhysicalScreen

00000900: UI:MuteOffPhysicalScreen

00000900: UI:AC:EnryPB

00000900: UI:AP:ChkCnctUSB

00000900: UI:DisplayPhysicalScreenCBR

00000900: UI:DisplayPhysicalScreenCBR

00002810: UI:ScreenLock

00002810: UI:ScreenUnLock

00002820: UI:DisplayPhysicalScreenCBR

« Last Edit: 31 / October / 2010, 13:47:20 by Bernd R »
Ixus 1000 HS

Re: IXUS 1000 HS Porting Thread
« Reply #65 on: 31 / October / 2010, 13:57:55 »
The V5 give same result as V4.

here is romlog of V5

Exception!! Vector 0x10
Occured Time  2010:10:31 18:54:20
Task ID: 16973859
Task name: SpyTask
Exc Registers:
0xE667FDE8
0xE59FF014
0x0038C22C
0x0038C198
0x001801DB
0x0018A958
0x00000002
0x00000001
0x19980218
0x19980218
0x19980218
0x0038C194
0x0038C198
0x0038C1A0
0xFF836DBC
0x001BA9F0
0x60000013
StackDump:
0x00000000
0x00372C08
0x0018E7F8
0x00372BB8
0x0038C1F0
0x00000001
0x000002E4
0x000000C6
0x00000001
0x19980218
0x0017B9AB
0x0017BBD1
0x00000191
0x19980218
0x0017BC91
0x19980218
0x00000001
0xFF8128AC
0x00000032
0xFF83B5B8
0x00000000
0x02FAF080
0x00000191
0x00000191
0x19980218
0x00000001
0x19980218
0x00172D31
0x00372BB8
0x19980218
0x19980218
0x0018EC38
0x19980218
0x0038C230
0xFF816B74
0x0018EC38
0x19980218
0x19980218
0x00001008
00000130: *** Camera Log Start ***

00000140: UI:_BeforeCBRForPlay

00000140: UI:_AfterCBRForPlay

00000150: UI:DSIC:55,0

00000150: UI:LogicalEvent:0x5003:adr:0,Para:0

00000150: UI:LogicalEvent:0x1165:adr:0,Para:0

00000150: UI:_SImage

00000150: UI:SetPanelBrightnessToLcdController

00000150: UI:SetDisplayType

00000150: UI:TurnOnDisplayForStartup

00000150: UI:LogicalEvent:0x5007:adr:0,Para:0

00000210: UI:LogicalEvent:0x5001:adr:0,Para:0

00000210: SS:S-Imag

00000230: UI:ScreenLock

00000230: UI:ScreenUnLock

00000230: UI:LogicalEvent:0x300a:adr:0,Para:0

00000230: UI:HDMIConnectCnt

00000230: UI:PB.Create

00000270: UI:PB.CreateE

00000270: UI:DisplayPhysicalScreenCBR

00000270: UI:DispSwCon_TurnOnBackLight

00000270: UI:TurnOnBackLight

00000340: UI:MuteOffPhysicalScreen

00000340: UI:LogicalEvent:0x3138:adr:0,Para:0

00000440: UI:LogicalEvent:0x5006:adr:0,Para:0

00000440: UI:AC:StartPB

00000440: UI:DispSwCon_TurnOnDisplayDevice

00000440: UI:AC:EBtn

00000440: UI:PB.Start

00000440: UI:DSIC:47,0

00000470: UI:CC_CompFlhJpg

00000470: UI:_CompFlhJpg

00000470: UI:PB.Flash

00000470: UI:ScreenLock

00000470: UI:DSIC:47,0

00000470: UI:ScreenUnLock

00000470: UI:ScreenLock

00000470: UI:DSIC:47,0

00000480: UI:LogicalEvent:0x3209:adr:0x12,Para:18

00000650: UI:PB.DrawI

00000670: UI:PB.StartE

00000670: UI:PB.TOTAL

00000670: UI:DisplayPhysicalScreenCBR

00000670: UI:LogicalEvent:0x320a:adr:0,Para:0

00000670: UI:PB.DPOF

00000720: UI:LogicalEvent:0x321f:adr:0,Para:0

00000720: UI:PB.CTG

00000760: UI:LogicalEvent:0x3203:adr:0,Para:0

00000770: UI:PB.DcdCBR

00000770: UI:DSIC:48,0

00000770: UI:PB.RfrsI

00000790: UI:LogicalEvent:0x3201:adr:0,Para:0

00000790: UI:ScreenUnLock

00000800: UI:DSIC:48,0

00000810: UI:DispSw: Unlock

00000810: UI:DispSwCon:Unlock

00000810: UI:DispSwCon_TurnOnBackLight

00000810: UI:DispSwCon_MuteOffPhysicalScreen

00000810: UI:MuteOffPhysicalScreen

00000810: UI:AC:EnryPB

00000810: UI:AP:ChkCnctUSB

00000810: UI:DisplayPhysicalScreenCBR

00002800: UI:ScreenLock

00002800: UI:ScreenUnLock

00002820: UI:DisplayPhysicalScreenCBR

   
Ixus 1000 HS

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #66 on: 31 / October / 2010, 15:08:57 »
Ok looks like we are at spytask!!, I mean you get no more errors at boot.c ?

now you need to comment all the lines at  core\main.c  in function core_spytask() to see where it fails
« Last Edit: 31 / October / 2010, 15:18:59 by asm1989 »

*

Offline reyalp

  • ******
  • 10057
Re: IXUS 1000 HS Porting Thread
« Reply #67 on: 31 / October / 2010, 15:18:26 »
Note, if you look at core/main.dump form your build tree (should be from the *exact* same build you are running), you can match up the addresses in the romlog (from the registers and/or stack dump) with source code, which may be quicker than trial and error.

Vector 0x10 is an invalid memory reference, e.g. the program tried to LDR from something that wasn't ROM, RAM or MMIO

Address of faulting in instruction in v5 dump -> PC=0x001BA9F0 which should be CHDK code.
Don't forget what the H stands for.


*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: IXUS 1000 HS Porting Thread
« Reply #68 on: 31 / October / 2010, 15:40:42 »
@Bernd R

I also notice that have the LED_PR copied from the sx210 and one of the two leds has a diferent address

change this in main.c at loader folder

Code: [Select]
#define LED_PR 0xC0220138   // -> ASM1989 10.31.2010 found at FF929B94,
http://www.4shared.com/file/NfFY_z_z/loader_ixus1000_maincv002.html

Re: IXUS 1000 HS Porting Thread
« Reply #69 on: 01 / November / 2010, 05:03:24 »
Note, if you look at core/main.dump form your build tree (should be from the *exact* same build you are running), you can match up the addresses in the romlog (from the registers and/or stack dump) with source code, which may be quicker than trial and error.

Vector 0x10 is an invalid memory reference, e.g. the program tried to LDR from something that wasn't ROM, RAM or MMIO

Address of faulting in instruction in v5 dump -> PC=0x001BA9F0 which should be CHDK code.

I search for all dump files and the file with highest address was core/main.dump

But the highest address in the list was this.SO code cant see here.

Is it possible that something is miss to dump(i use chdk shell and elfobjdump switch on), or the Camera Firmware have too code place on this Ram ?

chdk let set some Options.opt_MD_DEBUG i have off
OPT_DEBUGGING i have switch on.

OPT_LUA_CALLNATIVE is off


BTW: is it safe when i remove OPT_CURVES / OPT_CALENDER /OPT_GAME_XXX OPT_TEXTREADER

so maybe compiletime speed up more ?

001b1938 <sentinel_>:
  1b1938:   00000000 6f727265 6f6c2072 6e696461     ....error loadin
  1b1948:   6f6d2067 656c7564 73252720 72662027     g module '%s' fr
  1b1958:   66206d6f 20656c69 27732527 25090a3a     om file '%s':..%
  1b1968:   00000073 48432f41 532f4b44 50495243     s...A/CHDK/SCRIP
  1b1978:   002f5354 41554c2e 00000000 48432f41     TS/..LUA....A/CH
  1b1988:   4c2f4b44 494c4155 00002f42 6c657270     DK/LUALIB/..prel
  1b1998:   0064616f 63617027 6567616b 6572702e     oad.'package.pre
  1b19a8:   64616f6c 756d2027 62207473 20612065     load' must be a
  1b19b8:   6c626174 00000065 6f6e090a 65696620     table.....no fie
  1b19c8:   7020646c 616b6361 702e6567 6f6c6572     ld package.prelo
  1b19d8:   275b6461 5d277325 00000000 414f4c5f     ad['%s']...._LOA
  1b19e8:   00444544 706f6f6c 20726f20 76657270     DED.loop or prev
  1b19f8:   73756f69 72726520 6c20726f 6964616f     ious error loadi
  1b1a08:   6d20676e 6c75646f 25272065 00002773     ng module '%s'..
  1b1a18:   64616f6c 00737265 63617027 6567616b     loaders.'package
  1b1a28:   616f6c2e 73726564 756d2027 62207473     .loaders' must b
  1b1a38:   20612065 6c626174 00000065 00000000     e a table.......
  1b1a48:   75646f6d 2720656c 20277325 20746f6e     module '%s' not
  1b1a58:   6e756f66 73253a64 00000000 6b636170     found:%s....pack
  1b1a68:   00656761 64616f6c 00006465 70736944     age.loaded..Disp
  1b1a78:   5f766544 62616e45 7645656c 50746e65     Dev_EnableEventP
  1b1a88:   00636f72 70736944 5f6e6f43 6e727554     roc.DispCon_Turn
  1b1a98:   4466664f 6c707369 00007961 0049462e     OffDisplay...FI.

thats end

>I also notice that have the LED_PR copied from the sx210 and one of the two leds has a diferent address
>#define LED_PR 0xC0220138   // -> ASM1989 10.31.2010 found at FF929B94,

this work too(i test with the blink function), its same LED position, but diffrent color now.

« Last Edit: 01 / November / 2010, 05:08:20 by Bernd R »
Ixus 1000 HS

 

Related Topics