I been researching the CF card structure on how it communicates with the controller , is seem that
there a header (just like a Hard Drive) in that header is written configuration files & at what mode
it accesses , (e.g. mode 0-4) these mode are related to write/read speed & timing.
this is the
determent mostly by the device in this case the 5d2 canon write the table for dryOS uses.
is in "ns" nano seconds , so in a nut shell that the timing for read/write plus in this mode theses
more then write & read i/o there wait times
here a list what going on
the whole process can not take more then the total "I/O Pulse width" which is 1250ns
This where we/I can alter the timing band width for increased frequency ....... etc. ... more to come this
The above mode is for the CF card in "True IDE Mode" the cf card can run in 3 different configurations
True IDE Mode,PC Card Memory Mode,PC Card I/O Mode(this is from specification 2.0 so there's more then likely the more mode in the newer spec.
So to find the block that has the configuration on the CF card was my next step , so i made a CF card image (like a ISO) and read it in HxD Hex editor , didn't find that block yet but found something interesting , appertainy there more head timers involved then i thought .
I see 4 in total but we only use 2 so are we missing them ? or do we need them ?
this what i found
I've seem data from a1ex on 5d2 with 120Mb/s on CF card in a write test in a low level access
so there must be a lot of overhead going on.
There's 2 direction I'm looking at here reduce overhead (turn off unnecessary resources like "DFE face detection (must be part of the auto focus) e.g. and set it to UMDA7 (or over clock the cf bus)
If i can turn off some resources i can get 75-80Mb/s to go to at less 100Mb/s or 120Mb/s that the speed for UDMA 6 , UDMA 7 pushes that to 150Mb/s . The 5D3 is on a exfat which can access larger blocks of data so the 5D2 will never see UDMA 7 speeds without overclocking , fat32 will not allowed access speed in exfat file structure . Now that being said the theoretically fat32 is limited to 133Mb/s so 120Mb/s should be reachable
More to come ............
https://engineering.purdue.edu/ece477/Archive/2004/Spring/S04-Grp07/documentation/cfspc2_0_compact_flash.pdf
My sources of information
there a header (just like a Hard Drive) in that header is written configuration files & at what mode
it accesses , (e.g. mode 0-4) these mode are related to write/read speed & timing.
this is the
Code Select
CISTPL_CONFIG
Configuration Tuple is stored in the cf card header and isdeterment mostly by the device in this case the 5d2 canon write the table for dryOS uses.
Code Select
pLStorage=0x685504
is the reg on the card as seen in the start up log I've posted , & the mode it run at is in "ns" nano seconds , so in a nut shell that the timing for read/write plus in this mode theses
more then write & read i/o there wait times
here a list what going on
Code Select
t0 -Cycle time (min)
t1 -Address Valid to -IORD/-IOWR setup(min) (Mode3= 180ns Mode4= 120ns)
t2 -IORD/-IOWR (min)(Mode3= 30ns Mode4= 25ns)
t2 -IORD/-IOWR (min) Register (8 bit)(Mode3= 80ns Mode4= 70ns)
t2i -IORD/-IOWR recovery time (min) (Mode3= 80ns Mode4= 70ns)
t3 -IOWR data setup (min) (Mode3= 30ns Mode4= 20ns)
t4 -IOWR data hold (min) (Mode3= 10ns Mode4= 10ns)
t5 -IORD data setup (min) (Mode3= 20ns Mode4= 20ns)
t6 -IORD data hold (min) (Mode3= 5ns Mode4= 5ns)
t6Z -IORD data tristate (max)(Mode3= 30ns Mode4= 30ns)
t7 Address valid to -IOCS16 assertion (max) (Mode3= n/a ns Mode4= n/a ns)
t8 Address valid to -IOCS16 released (max) (Mode3= n/a ns Mode4= n/a ns)
t9 -IORD/-IOWR to address valid hold (Mode3= 10ns Mode4= 10ns)
tRD Read Data Valid to IORDY active (min), if IORDY initially low after tA (Mode3= 0ns Mode4= 0ns)
tA IORDY Setup time (Mode3= 35ns Mode4= 35ns)
tB IORDY Pulse Width (max) (Mode3= 1250ns Mode4= 1250ns)
tC IORDY assertion to release (max)(Mode3= 5ns Mode4= 5ns)
the whole process can not take more then the total "I/O Pulse width" which is 1250ns
This where we/I can alter the timing band width for increased frequency ....... etc. ... more to come this
The above mode is for the CF card in "True IDE Mode" the cf card can run in 3 different configurations
True IDE Mode,PC Card Memory Mode,PC Card I/O Mode(this is from specification 2.0 so there's more then likely the more mode in the newer spec.
So to find the block that has the configuration on the CF card was my next step , so i made a CF card image (like a ISO) and read it in HxD Hex editor , didn't find that block yet but found something interesting , appertainy there more head timers involved then i thought .
I see 4 in total but we only use 2 so are we missing them ? or do we need them ?
this what i found
Code Select
mv=1 res=0 crop=0 task=? pc=ff986cc4 addr=82d0 HEAD1 timer (start?).c0f0713c: 476 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1830 addr=8328 HEAD3 timer (ticks?).c0f07134: 4 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1830 addr=8330 HEAD3 timer (start?).c0f07150: 49c ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
crop=0 task=LiveViewMgr pc=ff8e1844 addr=8370 HEAD4 timer (ticks?).c0f15084: 10000 ISO=200 Tv=50 Av=56 lv=1 zoom=5 mv=1 res=0
Right now we use (this is crop mode) Code Select
c0f0713c (offset)475
c0f07150 (offset)49c
Code Select
c0f07134
c0f15084
are not being modified , could be causing more overhead ? in write speed .I've seem data from a1ex on 5d2 with 120Mb/s on CF card in a write test in a low level access
so there must be a lot of overhead going on.
There's 2 direction I'm looking at here reduce overhead (turn off unnecessary resources like "DFE face detection (must be part of the auto focus) e.g. and set it to UMDA7 (or over clock the cf bus)
If i can turn off some resources i can get 75-80Mb/s to go to at less 100Mb/s or 120Mb/s that the speed for UDMA 6 , UDMA 7 pushes that to 150Mb/s . The 5D3 is on a exfat which can access larger blocks of data so the 5D2 will never see UDMA 7 speeds without overclocking , fat32 will not allowed access speed in exfat file structure . Now that being said the theoretically fat32 is limited to 133Mb/s so 120Mb/s should be reachable
More to come ............
https://engineering.purdue.edu/ece477/Archive/2004/Spring/S04-Grp07/documentation/cfspc2_0_compact_flash.pdf
My sources of information