did anybody enabled interrupt in eboot? I am using xscale 27x and pb 5.0

Re: interrupt mode in eboot? by Yannick

Yannick
Fri May 27 01:59:20 CDT 2005

Why would you use interrupt in eboot ? When eboot runs, nobody else is
running, so you have all the CPU time you want.

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADENEO (ADESET)
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"mobilevil" <mobilevil@mobile.com> a écrit dans le message de news:
%23C2pq2nYFHA.2312@TK2MSFTNGP14.phx.gbl...
> did anybody enabled interrupt in eboot? I am using xscale 27x and pb 5.0
>
>



Re: interrupt mode in eboot? by mobilevil

mobilevil
Fri May 27 03:48:21 CDT 2005

well I am working with usb rndis image download, and i found that
EdbgOutputDebugString take more time then the that usbc allows... so packet
is lost.
i fixed that, by handling usbc interrupt inside of
EdbgOutputDebugString(OEMWriteDebugByte that is). that's quite dirty and i
don't feel like it too much.

"Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in message
news:uRWCdmoYFHA.3488@tk2msftngp13.phx.gbl...
> Why would you use interrupt in eboot ? When eboot runs, nobody else is
> running, so you have all the CPU time you want.
>
> --
> ----------------------------------------------------------------
> Yannick Chamming's (eMVP)
> ADENEO (ADESET)
> Windows Embedded Manager
> ychammings AT adeset DOT com>
> http://www.adeset.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
>
> "mobilevil" <mobilevil@mobile.com> a écrit dans le message de news:
> %23C2pq2nYFHA.2312@TK2MSFTNGP14.phx.gbl...
>> did anybody enabled interrupt in eboot? I am using xscale 27x and pb 5.0
>>
>>
>
>



Re: interrupt mode in eboot? by voidcoder

voidcoder
Fri May 27 04:11:42 CDT 2005

You have to implement exception handlers in
EBOOT code and then map them to address
0x00000000. Hey, You have full control over
MMU in EBOOT since You are running in
supervisor mode, you can do anything You
want at this point.


"mobilevil" <mobilevil@mobile.com> wrote in message
news:%23sSXajpYFHA.3584@TK2MSFTNGP12.phx.gbl...
> well I am working with usb rndis image download, and i found that
> EdbgOutputDebugString take more time then the that usbc allows... so
> packet is lost.
> i fixed that, by handling usbc interrupt inside of
> EdbgOutputDebugString(OEMWriteDebugByte that is). that's quite dirty and i
> don't feel like it too much.
>
> "Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in
> message news:uRWCdmoYFHA.3488@tk2msftngp13.phx.gbl...
>> Why would you use interrupt in eboot ? When eboot runs, nobody else is
>> running, so you have all the CPU time you want.
>>
>> --
>> ----------------------------------------------------------------
>> Yannick Chamming's (eMVP)
>> ADENEO (ADESET)
>> Windows Embedded Manager
>> ychammings AT adeset DOT com>
>> http://www.adeset.com
>> Tél : +33 (0)4.72.18.57.77
>> Fax : +33 (0)4.72.18.57.78
>> ----------------------------------------------------------------
>>
>> "mobilevil" <mobilevil@mobile.com> a écrit dans le message de news:
>> %23C2pq2nYFHA.2312@TK2MSFTNGP14.phx.gbl...
>>> did anybody enabled interrupt in eboot? I am using xscale 27x and pb 5.0
>>>
>>>
>>
>>
>
>



Re: interrupt mode in eboot? by mobilevil

mobilevil
Fri May 27 04:17:18 CDT 2005

? seems no... mainstone2's eboot is not in supervisor mode I suppose? I
couldn't read cpu clock speed settings in eboot's C code.
anyway I have fixed the problem and no longer want interrupt in eboot. hehe

"voidcoder" <voidcoder@yahoo.com> wrote in message
news:edz8ZwpYFHA.3188@TK2MSFTNGP09.phx.gbl...
> You have to implement exception handlers in
> EBOOT code and then map them to address
> 0x00000000. Hey, You have full control over
> MMU in EBOOT since You are running in
> supervisor mode, you can do anything You
> want at this point.
>
>
> "mobilevil" <mobilevil@mobile.com> wrote in message
> news:%23sSXajpYFHA.3584@TK2MSFTNGP12.phx.gbl...
>> well I am working with usb rndis image download, and i found that
>> EdbgOutputDebugString take more time then the that usbc allows... so
>> packet is lost.
>> i fixed that, by handling usbc interrupt inside of
>> EdbgOutputDebugString(OEMWriteDebugByte that is). that's quite dirty and
>> i don't feel like it too much.
>>
>> "Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in
>> message news:uRWCdmoYFHA.3488@tk2msftngp13.phx.gbl...
>>> Why would you use interrupt in eboot ? When eboot runs, nobody else is
>>> running, so you have all the CPU time you want.
>>>
>>> --
>>> ----------------------------------------------------------------
>>> Yannick Chamming's (eMVP)
>>> ADENEO (ADESET)
>>> Windows Embedded Manager
>>> ychammings AT adeset DOT com>
>>> http://www.adeset.com
>>> Tél : +33 (0)4.72.18.57.77
>>> Fax : +33 (0)4.72.18.57.78
>>> ----------------------------------------------------------------
>>>
>>> "mobilevil" <mobilevil@mobile.com> a écrit dans le message de news:
>>> %23C2pq2nYFHA.2312@TK2MSFTNGP14.phx.gbl...
>>>> did anybody enabled interrupt in eboot? I am using xscale 27x and pb
>>>> 5.0
>>>>
>>>>
>>>
>>>
>>
>>
>
>



Re: interrupt mode in eboot? by voidcoder

voidcoder
Fri May 27 04:39:09 CDT 2005

Thats not a problem at all. Just add the following lines to Your
startup code:

ldr r0, =(CPSR_Mode_SVC :OR: CPSR_I_Bit :OR: CPSR_F_Bit)
msr cpsr_c, r0

Now You are supervisor :)


"mobilevil" <mobilevil@mobile.com> wrote in message
news:etlilzpYFHA.3616@TK2MSFTNGP15.phx.gbl...
>? seems no... mainstone2's eboot is not in supervisor mode I suppose? I
>couldn't read cpu clock speed settings in eboot's C code.
> anyway I have fixed the problem and no longer want interrupt in eboot.
> hehe
>
> "voidcoder" <voidcoder@yahoo.com> wrote in message
> news:edz8ZwpYFHA.3188@TK2MSFTNGP09.phx.gbl...
>> You have to implement exception handlers in
>> EBOOT code and then map them to address
>> 0x00000000. Hey, You have full control over
>> MMU in EBOOT since You are running in
>> supervisor mode, you can do anything You
>> want at this point.
>>
>>
>> "mobilevil" <mobilevil@mobile.com> wrote in message
>> news:%23sSXajpYFHA.3584@TK2MSFTNGP12.phx.gbl...
>>> well I am working with usb rndis image download, and i found that
>>> EdbgOutputDebugString take more time then the that usbc allows... so
>>> packet is lost.
>>> i fixed that, by handling usbc interrupt inside of
>>> EdbgOutputDebugString(OEMWriteDebugByte that is). that's quite dirty and
>>> i don't feel like it too much.
>>>
>>> "Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in
>>> message news:uRWCdmoYFHA.3488@tk2msftngp13.phx.gbl...
>>>> Why would you use interrupt in eboot ? When eboot runs, nobody else is
>>>> running, so you have all the CPU time you want.
>>>>
>>>> --
>>>> ----------------------------------------------------------------
>>>> Yannick Chamming's (eMVP)
>>>> ADENEO (ADESET)
>>>> Windows Embedded Manager
>>>> ychammings AT adeset DOT com>
>>>> http://www.adeset.com
>>>> Tél : +33 (0)4.72.18.57.77
>>>> Fax : +33 (0)4.72.18.57.78
>>>> ----------------------------------------------------------------
>>>>
>>>> "mobilevil" <mobilevil@mobile.com> a écrit dans le message de news:
>>>> %23C2pq2nYFHA.2312@TK2MSFTNGP14.phx.gbl...
>>>>> did anybody enabled interrupt in eboot? I am using xscale 27x and pb
>>>>> 5.0
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>



Re: interrupt mode in eboot? by mobilevil

mobilevil
Fri May 27 10:54:55 CDT 2005

oh? i thought it will take an interrupt to change mode?
anyway i will test it sooner or later... thx

"voidcoder" <voidcoder@yahoo.com> wrote in message
news:OP$Cv$pYFHA.580@TK2MSFTNGP15.phx.gbl...
> Thats not a problem at all. Just add the following lines to Your
> startup code:
>
> ldr r0, =(CPSR_Mode_SVC :OR: CPSR_I_Bit :OR: CPSR_F_Bit)
> msr cpsr_c, r0
>
> Now You are supervisor :)
>
>
> "mobilevil" <mobilevil@mobile.com> wrote in message
> news:etlilzpYFHA.3616@TK2MSFTNGP15.phx.gbl...
>>? seems no... mainstone2's eboot is not in supervisor mode I suppose? I
>>couldn't read cpu clock speed settings in eboot's C code.
>> anyway I have fixed the problem and no longer want interrupt in eboot.
>> hehe
>>
>> "voidcoder" <voidcoder@yahoo.com> wrote in message
>> news:edz8ZwpYFHA.3188@TK2MSFTNGP09.phx.gbl...
>>> You have to implement exception handlers in
>>> EBOOT code and then map them to address
>>> 0x00000000. Hey, You have full control over
>>> MMU in EBOOT since You are running in
>>> supervisor mode, you can do anything You
>>> want at this point.
>>>
>>>
>>> "mobilevil" <mobilevil@mobile.com> wrote in message
>>> news:%23sSXajpYFHA.3584@TK2MSFTNGP12.phx.gbl...
>>>> well I am working with usb rndis image download, and i found that
>>>> EdbgOutputDebugString take more time then the that usbc allows... so
>>>> packet is lost.
>>>> i fixed that, by handling usbc interrupt inside of
>>>> EdbgOutputDebugString(OEMWriteDebugByte that is). that's quite dirty
>>>> and i don't feel like it too much.
>>>>
>>>> "Yannick Chamming's [eMVP]" <ychammings_nospam@adeset.com> wrote in
>>>> message news:uRWCdmoYFHA.3488@tk2msftngp13.phx.gbl...
>>>>> Why would you use interrupt in eboot ? When eboot runs, nobody else is
>>>>> running, so you have all the CPU time you want.
>>>>>
>>>>> --
>>>>> ----------------------------------------------------------------
>>>>> Yannick Chamming's (eMVP)
>>>>> ADENEO (ADESET)
>>>>> Windows Embedded Manager
>>>>> ychammings AT adeset DOT com>
>>>>> http://www.adeset.com
>>>>> Tél : +33 (0)4.72.18.57.77
>>>>> Fax : +33 (0)4.72.18.57.78
>>>>> ----------------------------------------------------------------
>>>>>
>>>>> "mobilevil" <mobilevil@mobile.com> a écrit dans le message de news:
>>>>> %23C2pq2nYFHA.2312@TK2MSFTNGP14.phx.gbl...
>>>>>> did anybody enabled interrupt in eboot? I am using xscale 27x and pb
>>>>>> 5.0
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>