DryOS - some success

jeff666

DataGhost
nothing substantial was changed besides this file and the entire SDHC handling + SDlock (which can be handled through the keyboard code, I read?

As stated by GrAnd the SDLock is just another switch and thus managed in the keyboard-handler.
You might even have some success by deleting the corresponding bit from the loop in spytask. The lines in the platform/generic/kbd.c are

#define SD_READONLY_FLAG (0x20000)
physw_status[2] = physw_status[2] & ~SD_READONLY_FLAG;

Cheers.

GrAnd

ewavr
edit: state updated, currently missing:
strncmp strchr strncpy strcat strrchr strtol strpbrk

Found "by the way".

strncpy                                     FFC0E84C   
strrchr                                     FFC71BCC   
strstr                                      FFD62534

ewavr

GrAnd
[code]strncpy FFC0E84C
strrchr FFC71BCC
strstr FFD62534
[/code]

Thanks.

Instead of opendir, readdir, closedir I found OpenFastDir (0xFFDC1B04), ReadFastDir (0xFFDC1B980) and CloseFastDir(0xFFDC1C6😎 - names are from VxWorks cameras. ReadFastDir is similar to readdir(), but:
- prototype is: int ReadFasrDir(DIR* d, struct dirent * de) - return 1 if "d" is valid argument
- don't fill buffer for deleted files
- can read non-latin (cyrillic, for example) filenames (or only DRYOS can this?)

Would do well to use these functions in VxWorks cameras.

edit: struct dirent contain file name (8.3), attributes, size and create/modification/access time:

struct dirent {
char name[13]; // in reality all members 4-byte aligned
unsigned long unk1;
unsigned char attrib;
unsigned long size;
unsigned long time1;
unsigned long time2;
unsigned long time3;
};

edit2: Also works fine on A710 (VxWorks).

edit3: Work continued,
NHSTUB(qsort, 0xFFD62A14)

intrinsic

DataGhost
Edit3: It does seem to be required, though... my camera won't boot when I replace STRD by STR or STRH or comment it out. If replacing it by two STR instructions fixes the problem, it seems that it does do the right thing then.

My cam boots fine running the code you published with the strd's substituted by str's, I would suggest that as your code will eventually end up in trunk and 3.4.6 is the recommended version for building trunk that you're better writing your code against that, it certainly seems to be something that's changed from 3.4.3 to 3.4.6.

jeff666

DataGhost wrote:
http://stack.dataghost.com/chdk/20080112-platform-s5is-sub-101b-boot.c

I had a look in the file, located the function(s) in the S5 and A720 firmware and found the function-path in the A720 firmware to be much simpler than in the S5. It's still more complex than it would be with VxWorks, thanks to the missing CreateTaskHookAdd.
I suggest we all go to our nearest canon dealer and whine about missing features 😀

If I'm awake enough this evening, I will port your code to the A720.

GrAnd wrote:
[code]strncpy FFC0E84C
strrchr FFC71BCC
strstr FFD62534
[/code]

ewavr wrote:
NHSTUB(qsort, 0xFFD62A14)

How do you find such functions? Great Work, btw.

Cheers.

GrAnd

jeff666
How do you find such functions? Great Work, btw.

Accidentally... 😁
Found some similar functions in A610 and A720 firmwares, which uses stdlib functions. Then checked the calls sequences.
For ex, a function in A610 calls the functions:

 unknown
 strlen
 strstr
 strlen
 strcpy
 unknown
 strrchr
 strncpy

The same function in the A720:

 unknown
 strlen
 unknown
 strlen
 strcpy
 unknown
 unknown
 unknown

So, it's quite understandable which 'unknown' should be what. 😀

ewavr

jeff666
How do you find such functions?

I found some function (sub_FFCAD560 in a720, sub_FFE59E00 in a710), which calls qsort() - near "Dataset.c" string. qsort() in a710 and a720 not too similar, but I tested it in a720, it works.

Work continued, found (and tested):

NHSTUB(strncmp, 0xFFC71B5C)
NHSTUB(strchr, 0xFFC71BA😎
NHSTUB(strcat, 0xFFC71B20)
NHSTUB(strtol, 0xFFC1FC0C)

But strpbrk() not found 🙁

is*() functions did not exist in a720 (replaced by macros) - compare sub_FFCA625C in a720 and sub_FFE4C96C in a710. Requires its own implementation of these functions - via lookup table? (like this and this)

Currently not found: time, localtime, utime, strpbrk (or its replacement).

edit: NHSTUB(time, 0xFFC55F0C) == Time
instead of localtime() I found LocalTime(): NHSTUB(LocalTime, 0xFFC5605😎: struct tm * LocalTime(const unsigned long *, struct tm *);
struct tm is the same as in VxWorks (stdlib).
strpbrk() implementation can be found here - or copied from VxWorks firmware.

need: utime()

DataGhost

Small (depends on your viewpoint, though) update on the S5: the keyboard will now do whatever I want, OS functions still supported 😀 The code still looks like a complete mess, though, it doesn't even run in it's own task yet. Currently, it's constantly called from within the gui functions, since I could not get a proper task hook going before, so I placed all my code in there. Still loads of work to do, but I'm getting closer and closer 😀

lukg

Great Dataghost! do you think that your final working chdk will work even in firmware v1.00a?

DataGhost

I'm fairly certain that it won't. If they added just a couple of lines, it would screw up *all* alignment in the rest of the code. Once I get this done, though, I could have a look at the 1.01a firmware... (wait, did you say 1.00a? I'll need a dump for that) ...and point the code to the right addresses, as the differences shouldn't be as big as S5 <--> A720 😀 This will still require time, though, and personally I think there are enough people here, with at least limited knowledge, who can do this based on the code I'm producing, so I probably won't have to do that. I'll first have to get the rest working and clean up my code, though, I'm constantly changing stuff around 😀

lukg

I said 1.00A??? 😁 It was 1.01a sorry...anyway, thanks for your reply and for your great work (jeff too)

jeff666

Minor Update: SDHC with bootdisk support for A720

I included DataGhost's fat32-autodetect to allow booting from large cards.

You need to create two partitions on the card
1st: small only for chdk, this will boot, part-type 6, fat16 formatted
2nd: rest of the card for images, part-type 0x0b, fat32 formatted

Bad news for windows-users: Windows uses only the first partition on removable devices. Suggestions to solve this problem are appreciated.

The attached file belongs to platform/a720/sub/100c/

@ewavr: no changes have been made before "// SDHC-Boot-Support" and there are no external dependencies.

Cheers.

boot.c

60.79KB

DDMan

Fantastic news, Jeff! :😀

intrinsic
Something else I've noticed, there are some oddities to the DryOS branch which prevent it from building on the windows tool chain (gets stuck in an infinite loop and eventually sh.exe crashes).

The same here with me and gcc-3.4.6 toolchain on a Windows system (I know Windows is evil and doesn't like open source freeware to be compiled on it ) 😎! ???

I think this needs sorting out.

If I can provide any information, please contact me.

Greetz 🧑‍🎄

cedricb

for the partition issue on M$, why don't you use the other way around?

1st: FAT32
2nd: FAT16 to boot from

GrAnd

cedricb
for the partition issue on M$, why don't you use the other way around?

1st: FAT32
2nd: FAT16 to boot from

Because a camera wont boot from the second partition, I think.

DataGhost

Indeed. As you can see here, I have done some thorough research into solving this problem. The camera and Windows do the exact same thing (as can be seen in the code), where the camera is relatively easily modified to read the proper partition after booting. They both expect an SD card to have just one partition, they don't even check the partition type.

lukg

A couple of years ago i found a windows driver made by someone i don't remember that allows that...hope to find again. (maybe some 3rd party File Viewer could solve this problem?)

DataGhost

I've also been thinking about that, yes. I suggest we continue this conversation in the other thread, this doesn't only apply to DryOS cameras and is a bit offtopic in here 😀

ewavr

Attempt to port Allbest build to a720 - http://ewavr.nm.ru/hdk/allbest-a720-001.zip (src&bin)
Still without dual partitions support, utime(), some variables, USB remote button support and extended movie capabilities. >🙁
Testing and work continues...

p.s. platform/a720/sub/100c/boot.c: long canon_bss_len = 0x9d024 - 0xfc04; (After two days of trying to understand why not start CHDK in Allbest/Grand build)

lukg

😐: i didn't know you are in such advanced state...is shooting raw working too?

« Previous Page Next Page »