Here's a CHDK-less SD benchmark.
loaded A/CBBENCH.BIN size 132 at 0x005325c0time 2770 speed 46 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/stime 2930 speed 43 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/smin 2770 max 2940 avg 2917 avg speed 43 MB/s
Quote from: reyalp on 01 / May / 2017, 00:57:58Here's a CHDK-less SD benchmark.Thanks. I finally had the chance trying it.Here is a typical run (from CBasic), using a Sony branded 16GB (UHS-I, U1, "94MB/s") card that looks similar to this:Code: [Select]loaded A/CBBENCH.BIN size 132 at 0x005325c0time 2770 speed 46 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/stime 2930 speed 43 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/stime 2940 speed 43 MB/smin 2770 max 2940 avg 2917 avg speed 43 MB/sIt looks like 43MB/s is the maximum writing speed that can be expected (cam was the M10, same results with/without CHDK + card reset hack). Apparently, "we" did not get the same card speed as the 80D.
The CHDK benchmark module's results are much worse and fluctuating.
It looks like 43MB/s is the maximum writing speed that can be expected (cam was the M10, same results with/without CHDK + card reset hack). Apparently, "we" did not get the same card speed as the 80D.
Do you have logs for this card?What is the second value in message "USetAcMd(%d,%d)s" ?
Sony 16G UHS-I U1, "94MB/s"SetSSCG(12,0)sHWInit(0)sSWInit(0)sSetUHSMod(0,1)sRegPowCF(0)sCardInit(0)sGetCrdTyp(0)sGetCmnReg(0)sSdGetReg(0)sGetRUS(0)sGetSpd(0)sUGtSuAcMd(0)sUSetAcMd(0,3)sUGtSuCuLm(0)sUSetCuLm(0,2)sChgClkSpd(0,8)sUTuSmPt(0,0)sGetTtlSect(0)sKingston 16G UHS-I U1, "90MB/s R 45MB/s W"SetSSCG(12,0)sHWInit(0)sSWInit(0)sSetUHSMod(0,1)sRegPowCF(0)sCardInit(0)sGetCrdTyp(0)sGetCmnReg(0)sSdGetReg(0)sGetRUS(0)sGetSpd(0)sUGtSuAcMd(0)sUSetAcMd(0,3)sUGtSuCuLm(0)sUSetCuLm(0,2)sChgClkSpd(0,8)sUTuSmPt(0,0)sGetTtlSect(0)sSandisk 16G UHS-I U1 "48MB/s"SetSSCG(12,0)sHWInit(0)sSWInit(0)sSetUHSMod(0,1)sRegPowCF(0)sCardInit(0)sGetCrdTyp(0)sGetCmnReg(0)sSdGetReg(0)sGetRUS(0)sGetSpd(0)sUGtSuAcMd(0)sUSetAcMd(0,2)sUGtSuCuLm(0)sUSetCuLm(0,1)sChgClkSpd(0,6)sUTuSmPt(0,0)sGetTtlSect(0)s
It might make more sense to start with uncached + 1 MB or something like that.
It would be interesting to see what results you get on sx280.
loaded A/CBBENCH.BIN size 132 at 0x0041dd88time 6330 speed 20 MB/stime 7450 speed 17 MB/stime 7490 speed 17 MB/stime 7490 speed 17 MB/stime 7510 speed 17 MB/stime 7910 speed 16 MB/stime 7610 speed 16 MB/stime 8410 speed 15 MB/smin 6330 max 8410 avg 7525 avg speed 17 MB/s
' run benchmark binary^M' sd card information function, set to 0 to skip^MDIM SdInfo_ptr = 0x10e7e3d^M'DIM SdInfo_ptr = 0^M' addresses below from funcs_by_*.csv^MDIM Open_ptr = 0xfc3328e9^MDIM Write_ptr = 0xfc3329a5^MDIM Close_ptr = 0xfc33296d^MDIM GetSystemTime_ptr = 0xfc3a46a9
Trying to benchmark my SX60 before making changes to boot.c (as @reyalp did in the latest g7x build)It's been a long time since I ran canon basic...something is wrong.I rebuilt cbbench.bin (I don't think I had to)I edited extend.m for SX60HS/100f pointersCode: [Select]' run benchmark binary^M' sd card information function, set to 0 to skip^MDIM SdInfo_ptr = 0x10e7e3d^M'DIM SdInfo_ptr = 0^M' addresses below from funcs_by_*.csv^MDIM Open_ptr = 0xfc3328e9^MDIM Write_ptr = 0xfc3329a5^MDIM Close_ptr = 0xfc33296d^MDIM GetSystemTime_ptr = 0xfc3a46a9put cbbench.bin and extend.m onto the card.....script.req looks ok.BUT...when I press set, I still get a message from romlog dump program...and then the camera crashes....
' hokey attempt to get ensure loaded binary is out of cache memset(cachbuf,0xab,cachbuf_size) Wait(100) memset(cachbuf,0xba,cachbuf_size)
Change cachbuf to cachebuf, cachbuf_size to cachebuf_size.
only one copy of extend.m no caps EXTEND.M. If the new extend.m contains a syntax error, does the last successful extend.m prevail somewhere in memory?
Maybe I'll just give up and use the standard benchmarks already in CHDK.