Re: SDSynchronousBusRequest taking long time


> Can you suggest me how to go through the debugger? The code runs on a
> Windows Mobile device. Currently I am debugging by writing to a file. I
>

Well, if you have no possibility to debug on the target device
it is getting more complicated. There are not too much things
you can do about it on a ready made WM5 device. Especially because
the bottleneck may be in the lower level sdcard host controller
driver (device specific) and not in the sdbus driver
or sdcard lib (device independent thing). Try different
WM devices, try to analyze sdcard sources, fortunately you have
PB installed. Look here:

....\WINCExxx\PUBLIC\COMMON\OAK\DRIVERS\SDCARD\SDBUS\*


It is definitely worth buying a development KIT if you
want to untie your hands. Try to google around, there
are enough devkits with SDCARD on board and Windows CE
support ...


--
Oleg


Advait wrote:
Sorry I was not aware that I could taget multiple groups in "to" field.
Can you suggest me how to go through the debugger? The code runs on a Windows Mobile device. Currently I am debugging by writing to a file. I thought SDSynchronousBusRequest is a call in a library provided by Microsoft. How can I step through? I am new to Platform builder.
Thanks for your help.

"voidcoder" wrote:

Why not just step in debugger and see where
it spends so much time?

Also separate cross posting is evil. List all
target groups in "to" field if you want to post
to multiple groups.


--
Oleg


Advait wrote:
Hi,

From the SDIO driver we get from Arasan they use SDSynchronousBusRequest() to issue a bus request to their chip.

We timestamp before and after calling this API, and it takes > 230ms. Why it takes so long and how can we make it

much faster? The following are the code sample:

SDSynchronousBusRequest(pDevice->hDevice, SD_CMD_IO_RW_EXTENDED,
argument,
SD_WRITE, ResponseR5,
&response, 1,
blockLength , pBuffer,
0);



where:

argument = BUILD_IO_RW_EXTENDED_ARG(SD_IO_OP_WRITE, SD_IO_BLOCK_MODE, pDevice->Function, wAddress, SD_IO_FIXED_ADDRESS, 1);

SD_COMMAND_RESPONSE response

Your kind responses are greatly appreciated.

.

Relevant Pages

  • Re: DPMI raw mode switch
    ... > 2F, and since that's how you begin any startup procedure with DPMI, it ... when writing DOS software I ... use the WD (Watcom Debugger) from the WATCOM C++ 11.0c compiler package. ...
    (alt.lang.asm)
  • Re: getting good at assembly language
    ... Ludwig wrote the following useful and helpful info - ... And writing assembly entices to get dirty in your code ... >> Again true, a debugger would require a lot of good OS knowledge, ... Thanks for that, maybe I will aim towards a kernel debugger, I've ...
    (alt.lang.asm)
  • Re: Top ten errors
    ... >> But the debugger issue hits one of my buttons. ... > writing functions or code snippets which are to be removed in the final ... thrown away (yes, even 'correct', working code). ... was the learning experience, not the code itself. ...
    (alt.comp.lang.learn.c-cpp)
  • Re: getting good at assembly language
    ... > writing such tools I don't think allows for sloppy design or coding ... > Again true, a debugger would require a lot of good OS knowledge, ... writing something like www.ollydbg.de is ... > need to ease myself in gently by getting stuck into assembler once ...
    (alt.lang.asm)
  • Re: edit & continue
    ... restarting the whole app than trying to jump back that far(if its even ... > check it for mistakes is to run it. ... I simply said I don't use the debugger enough to ... they are writing, catching the little mistakes that are left behind. ...
    (microsoft.public.dotnet.languages.csharp)