MPC574XX uSDHC_DriverIRQHandler ()

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MPC574XX uSDHC_DriverIRQHandler ()

5,677 Views
2548903578
Contributor III

Hi,

Why does "No source available for" uSDHC_DriverIRQHandler () at 0x1002bc8 "appear during debugging

微信截图_20200413141611.png

0 Kudos
Reply
18 Replies

4,706 Views
petervlna
NXP TechSupport
NXP TechSupport

Hi,

the possible reasons are:

1. You added files to project after compilation

2. you did not compiled it with debug info

3. there is only binary for that SD library.

can you find that function in your project?

regards,

Peter

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

Can I understand that some configuration files are missing in my project?

0 Kudos
Reply

4,706 Views
petervlna
NXP TechSupport
NXP TechSupport

Hi,

That is possible, however I am not able to confirm.

But since you have binary in your code, you are either missing debug information or you did not compiled the project correctly.

regards,

Peter

0 Kudos
Reply

4,706 Views
dsytj88
Contributor II

hi Peter

I have the same problem,basing on the example of freeRTOS(SDK 3.0) for MPC5748G,I add some functions

for CAN bus.

1,the compiling is success;

2,elf file is generated;

3,in debug mode, after initializing clock,flexcan,then I want to install one callback function for FlexCAN,

after entering into FLEXCAN_DRV_InstallEventCallback,at the end of this function,some error happened.

void FLEXCAN_DRV_InstallEventCallback(uint8_t instance,
                                      flexcan_callback_t callback,
                                      void *callbackParam)
{
    DEV_ASSERT(instance < CAN_INSTANCE_COUNT);

    flexcan_state_t * state = g_flexcanStatePtr[instance];

    state->callback = callback;
 state->callbackParam = callbackParam;
}

the error is "No source available for "uSDHC_DriverIRQHandler() at 0x1002bc8" ", do you have any sollution?

thank you.

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

If you don't use an operating system, can CAN work properly?

0 Kudos
Reply

4,706 Views
dsytj88
Contributor II

hi,if apply callback function without freertos,it's ok.

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

I would like to ask you which function you blocked

0 Kudos
Reply

4,706 Views
dsytj88
Contributor II

now this issue is resolved,the reason is due to limited resource.

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi, friend

   Can you tell me how you solved this problem?

0 Kudos
Reply

4,706 Views
dsytj88
Contributor II

increase the heap/stack size.

2,677 Views
turkmani_11
Contributor III

can you please show how did you increase it?

 

0 Kudos
Reply

3,968 Views
liguangyu02
Contributor II

My issue fixed after increasing heap/stack size.

Thanks for community!

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

I modified these two places and found it still not working.微信截图_20200512145122.png微信截图_20200512145113.png

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

How did you solve it

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

I suggest you can take a look at this article, it may be helpful to you.

https://community.nxp.com/thread/390114 

0 Kudos
Reply

4,706 Views
petervlna
NXP TechSupport
NXP TechSupport

Hi,

Are you using interrupts via OS or via the custom vector table?

I have feeling that you guys are not handling properly interrupts in OS. All ISRs must go trough OS.

regards,

Peter

0 Kudos
Reply

4,706 Views
dsytj88
Contributor II

hi

the user interrupt table is used in this demo.I checked in PE for FreeRTOS, there is no place for ISR, only see the collum for hook to enable or disable.

in interrupt manager(processor expert),it seems I can't change anything. as you mentioned,if all the ISR should go through OS,

may you pls give some more comments or some detailed introduction is preffered.

thank you

0 Kudos
Reply

4,706 Views
2548903578
Contributor III

Hi,

Does this require us to manually modify the OS takeover interrupt

0 Kudos
Reply