SX720 Porting thread - page 14 - DryOS Development - CHDK Forum supplierdeeply

SX720 Porting thread

  • 158 Replies
  • 40895 Views
*

Offline srsa_4c

  • ******
  • 4031
Re: SX720 Porting thread
« Reply #130 on: 23 / April / 2016, 10:55:32 »
Advertisements
Thanks uncommented that but still see no info if enble debubug in the menu can see the props and so on, when should I see it?
Miscellaneous stuff -> Debug parameters -> Show misc values

If modules are working now, you could try running Miscellaneous stuff -> Tools -> CPU INFO to get camera CPU (and configuration) data.

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX720 Porting thread
« Reply #131 on: 23 / April / 2016, 11:16:50 »
Great thanks, got the value changes now need to convert them to the mask


CPUINFO attached!  :D what can we use it for?

*

Offline srsa_4c

  • ******
  • 4031
Re: SX720 Porting thread
« Reply #132 on: 23 / April / 2016, 11:21:05 »
CPUINFO attached!  :D what can we use it for?
You can compare it to the one from g7x for example. The MPU (memory protection unit) setup is expected to differ somewhat.

edit:
MPU setup is the same, including the protected 32 bytes starting at address 0. However, it's now official that the 0xbfe10000 area is the BTCM which was configured to 0x80000000 on older D6 cams.
« Last Edit: 23 / April / 2016, 11:25:10 by srsa_4c »

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX720 Porting thread
« Reply #133 on: 23 / April / 2016, 11:28:49 »
yes these are the only differences



155c155
< BTCM region reg 0xBFE1001D
---
> BTCM region reg 0x8000001D
160c160
<   Base address         0xBFE10 785936 [0xbfe10000]
---
>   Base address         0x80000 524288 [0x80000000]



*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX720 Porting thread
« Reply #134 on: 23 / April / 2016, 11:29:30 »
Did I need to change something in my sources?




*

Offline srsa_4c

  • ******
  • 4031
Re: SX720 Porting thread
« Reply #135 on: 23 / April / 2016, 11:31:11 »
Did I need to change something in my sources?
Due to CPUINFO? No.

*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX720 Porting thread
« Reply #136 on: 23 / April / 2016, 11:33:06 »
Ok, thanks, any clue how to debug why overrides are not working?




*

Offline srsa_4c

  • ******
  • 4031
Re: SX720 Porting thread
« Reply #137 on: 23 / April / 2016, 11:41:02 »
Ok, thanks, any clue how to debug why overrides are not working?
I don't see the source, so, guessing.
- You're not actually overriding the firmware's capt_seq task due to some programming mistake.
- The hooks are placed at incorrect locations. There's a script: chdk/scripts/test/hooktest.lua that can be used to determine whether hooks are called.


*

Offline asm1989

  • *****
  • 527
  • SX720, SX260, SX210 & SX200
Re: SX720 Porting thread
« Reply #138 on: 23 / April / 2016, 11:50:32 »

Here are the latest sources  http://filebin.net/rw32z7gmyl


hooktest.lua hangs the cam attached romlog

*

Offline srsa_4c

  • ******
  • 4031
Re: SX720 Porting thread
« Reply #139 on: 23 / April / 2016, 17:36:51 »
hooktest.lua hangs the cam attached romlog
I'm not sure the romlog is related. The crash it shows happened ~1.2 seconds after camera start. It's an "undefined instruction" exception, the addresses (PC, LR and most of what's on stack) could be inside a module, not sure why.
"Undefined instruction" could be caused by incorrect thumb state, division by zero or due to executing garbage.

capt_seq.c seems full of reyalp's debug code, you could try using it (you need to access the syslog for those debug messages).

 

Related Topics