Messages

Hi guys, you can find the cache_hack i've made, in my repo, if you wanna try:
I think it is here: https://bitbucket.org/xaint/ml/commits/f3631da68349f1dda86ee136bbddc5a3c4efc9bc
Try it on your own risk (for me it's pretty stable) :D

Whoa ! BINGOOO !!! Great work !!! Here we  are !!! Finally !!!     

not yet, Alex scared me when he came in at that point.

Don't worry, what I'm sayng to you are hints directly from 1% that replied to me in a private msg ! 

So, proceed with my last hint about makefile and take note about the #ifdef of my last post... we are so close ! 

[Also, very important]

Right now we are trying to figure out Hijack Cache

Also, very important :

don't forget to replace ifdef 6D with
#ifdef HIJACK_CACHE_HACK_ALLOCMEM_SIZE_ADDR in boot-hack.c and get rid of allocate mem in internals.h

Right now we are trying to figure out Hijack Cache

Have you done my last hint ? Do it works ?

Why are you messing with this in the first place?!

? what is wrong ? 

That boots cam but ML doesnt load at all.

Ok, you have to go to the ML source directory PLATFORM/550d.109 and edit the file named "Makefile" : find the line "#RESTARTSTART = 0xC80100" and change the old pre-existent value to the new value (HIJACK_CACHE_HACK_BSS_END_INSTR + 100)

So we know that :
#define HIJACK_CACHE_HACK_BSS_END_INSTR 0xE3A018C6   
And hence :
0xE3A018C6 + 100 = 0xE3A019C6
And so, finally :
#RESTARTSTART = 0xE3A019C6  (into Makefile)

That leads to no boot with just red flashing light.

have you added also : #define HIJACK_CACHE_HACK_INITTASK_ADDR             0xFF018D1C       ?

I think we just need these addresses to make it fit our firmware, if I am right?
#define HIJACK_CACHE_HACK_BSS_END_ADDR   0xFF01109C
#define HIJACK_CACHE_HACK_BSS_END_INSTR  0xFF010134

If you have Windows, follow my advice in the head post here (I keep it updated very frequently!!) , in order to disassemble directly from Windows !

Also, i found these instructions in our ROM1.BIN that "1%" user says are the start and end of allocation memory: i hope they are what we are searching for :

0xFF011CB4     E3A0160D     MOV R1,#0xD00000 (start address of allocation memory ?)
0xFF011CB8     E3A0083D     MOV R0,#0x3D0000 (end address of allocation memory ?)

So 1% says to subtract the value 0xA0000 (640k) to both 0xD00000 and 0x3D0000 values
0D00000 - A0000 = C60000

From tragic lantern for 600D we have :
---------------------------------------------------------------------------------
//MOV     R1, #0xD00000 C60000
// load ML in the AllocateMemory pool
#define HIJACK_CACHE_HACK_BSS_END_ADDR 0xFF0123E4
//0xA0000 - 640K Should Be enough for everyone
#define HIJACK_CACHE_HACK_BSS_END_INSTR 0xE3A018C6


//~ MOV     R0, #0x3D0000 330000
//~ fixup start address of AllocateMemory pool 0x8F0000
#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_ADDR 0xFF0123E8
//0x7D0000
#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_INSTR 0xE3A00833
-----------------------------------------------------------------------------------

So, for us, we should have :
#define HIJACK_CACHE_HACK_BSS_END_ADDR 0xFF011CB4           <- Our address of the first instruction
#define HIJACK_CACHE_HACK_BSS_END_INSTR 0xE3A018C6   <- The machine code of new value (start value)
#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_ADDR 0xFF011CB8  <- Our address of the second instruction
#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_INSTR 0xE3A00833  <- The machine code of new value (end value)

The machine-codes of 600D and 550D are the same, because they have the same processors and so same instructions-sets and coding for them.

And don't forget this value also, specific for our 550D :

#define HIJACK_CACHE_HACK_INITTASK_ADDR             0xFF018D1C     

Just when I found out how to dump the ROM from the correct address 0xFF010000 X-)

Do you have found the disassembly start address of both ROM files ? And what they are ?
Do you have found what is the rom file where there is the stuff we are searching for ? ROM0.BIN or ROM1.BIN ?

Just when I found out how to dump the ROM from the correct address 0xFF010000 X-)

Good ! Keep on with the good work ! This will be of help for future needs of disassebly for future features and needs ! I added this info to the header post ! Many thanks !

what does this cache hack can do?

It allows to use the raw video feature without disabling other features, like now. So no more need to have two different sd cards (one for raw video and one for all the other ML features). Only one .bin file, only one version ! It allows to have more memory to fit all the ML stuff together with raw video recording option !

ok: good news: the cache hack is seems to be working, checking now...

Wow xaint ! I cannot believe !!! You are Always ahead ten miles ! Keep me informed about your checks results ! 

Thanks xaint ! Happy to see you there ! 

I'm keeping the info at header as updated and correct as possible, as I progress with my knowledge and integrating with the Others programmers knowledge, but many obscure points remains... for example: the comments say: "0xA0000 - 640k should be enough for everyone" (that's ok, 0xA0000 is the value equivalent to 640kbytes), but the next line relative to this comment is "#define HIJACK_CACHE_HACK_BSS_END_INSTR 0xE3A018C6" ...    what is the connection of value 0xE3A018C6 with 0xA0000 ?!?    Do this is the line that defines the quantity of reserved memory (640k) ? And how ? 

For example, 600D has the following values, and it seems that "allocmem" values are not needed at all (not present in 600D CONSTS.H file)... am I wrong ?!? Or do we need them for 550D ? :

#define HIJACK_CACHE_HACK_BSS_END_ADDR 0xFF0110D0
#define HIJACK_CACHE_HACK_BSS_END_INSTR  0xE3A01732
#define HIJACK_CACHE_HACK_INITTASK_ADDR 0xFF0110DC

[?]

Hi programmers !

I need a three hints to find three values in the ROM: they are marked as ? in the head post of this thread. So we can start the hunt together !

Many thanks to all for your efforts ! 

Awesome work!

I am now able to get 960x512@24fps and 1280x400@24fps, using Hacked Mode with 720p@50 fps canon setting in video mode. Using a Sandisk 32GB 95Mb/s.

Someone here stated that in 720p Canon mode, the raw video has some sprinkles on it... some little pixels appearing and disappearing: can you confirm this or not ? Many thanks !

What I don't understand yet: 1% does for the 600D:

Code Select Expand

#define HIJACK_CACHE_HACK_ALLOCMEM_SIZE_ADDR 0xFF0123E8
But with the offsets from above, I dont't have such high addresses in my ROM?.BIN.dis

Many thanks for your hints ! Are you also working on this problem on 550D ? If yes, you can take hints on the head post of this thread, and if you have more hints to give, you can write them here so I will add them to the head post, many thanks !
Obviously you can tell me to modify-correct-integrate the infos that are already present there !

For your question: are you sure it's an offset (relative address) or perhaps it's an absolute address ?

Ok, I collected some info around the forum about this problem and I updated the head post, just in case someone is interested to help out. And now I need now some info to proceed :

Where to find the 550D rom disassembled, or where to find the rom dump and how to disassemble it ? Many thanks !

Excuse me, boys, but we programmers must solve the boot memory allocation problem, so no more double .bin is needed...

Look at what was done to boot-hack.c and 600D consts.h
https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/commits/all

Its booting into allocate pool and uses 640K bins. Just have to find the addresses in 550D firmware.

Do you mean HIJACK_CACHE_HACK and his addresses in 600D consts.h ?!?

Great Murphy ! Many thanks from me and all the ML community for sharing your great work ! 

Great, xaint ! Many thanks !

I can confirm the 550D ports about the title of this thread are now merged in the nightly build !

So... if no more problems arise about this, I will wait a little and then I will mark this thread with the prefix [DONE] ! 

Always special thanks to "xaint" and his successful efforts ! 

@Xaint : you said, some posts ago, that zebras seems not to be aligned. Can you confirm this or do they are ok ? Many thanks ! 

I used the one from this page

https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads
[600D] Still Sprinkle Free.zip   281.4 KB   2013-05-27   153

Thanks. Unfortunately it's a compiled version. I need the sources of this version, but i cannot find them inside the commits. Do this correction was already merged into the official ML nightly build ? If yes, I can check in the official repository current sources.

I would love that

I would love that also !!! 

No bad pixels on sensor!

Its the same issue on 600d that was fixed

see spinkle fix build 600d...

I tried to search the forum for this 600d fix, but I cannot find it. Can you give a link ? So I can try to port the fix into 550d also ! Many thanks !