• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 441 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

double load issue - ndk2 - dm648

Amna Rasul
Intellectual 900 points

hello all

I am working on ndk 2 :helloWorld project with my DM648 EVM . here is the issue the code doesnt run everytime i load it.    Sometimes it behaves like this

  1. On loading once , the code might hold after printing the following lines

                                        

                                        TCP/IP Stack 'Hello World!' Application

                                        Using MAC Address: 00-21-ba-12-5a-0f

                and on halting the code - the code pointer is pointing on UTL_halt    

 

when this happens i have to reload the code and run it again - n this kind of issue occurs random but occurs all the same

 

i have collected the following info - mayb someone can guide me to a solution

 

Test 1 :  Stops after this   

TCP/IP Stack 'Hello World!' Application

Using MAC Address: 00-21-ba-12-5a-0f

 20   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

21   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

22   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

23   SEM: post <unknown handle> (0xe0062c04) count = 0

24   SEM: post <unknown handle> (0xe0062c04) count = 0

25   SEM: post <unknown handle> (0xe0096d34) count = 0

26   CLK: current time = 4 (0x00000004)

27   PRD: tick count = 4 (0x00000004)

28   SWI: post  PRD_swi (0xe00cfeec)

29   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

30   SWI: begin PRD_swi (0xe00cfeec)

31   PRD: end

32   SWI: end   PRD_swi (0xe00cfeec) state = done

33   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

34   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

35   SEM: post <unknown handle> (0xe0062c04) count = 0

 

Test 2: Works well

104846   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

104847   CLK: current time = 17193 (0x00004329)

104848   PRD: tick count = 17193 (0x00004329)

104849   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

104850   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

104851   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

104852   CLK: current time = 17194 (0x0000432a)

104853   PRD: tick count = 17194 (0x0000432a)

104854   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

104855   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

104856   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

104857   CLK: current time = 17195 (0x0000432b)

104858   PRD: tick count = 17195 (0x0000432b)

104859   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

104860   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

104861   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

 

Test 3:fails again

25   SEM: post <unknown handle> (0xe0096d34) count = 0

26   CLK: current time = 4 (0x00000004)

27   PRD: tick count = 4 (0x00000004)

28   SWI: post  PRD_swi (0xe00cfeec)

29   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

30   SWI: begin PRD_swi (0xe00cfeec)

31   PRD: end

32   SWI: end   PRD_swi (0xe00cfeec) state = done

33   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

34   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

35   SEM: post <unknown handle> (0xe0062c04) count = 0

36   CLK: current time = 5 (0x00000005)

37   PRD: tick count = 5 (0x00000005)

38   SWI: post  KNL_swi (TSK scheduler) (0xe00cfec0)

39   SWI: begin KNL_swi (TSK scheduler) (0xe00cfec0)

40   SWI: end   KNL_swi (TSK scheduler) (0xe00cfec0) state = done

 plz guide me as to what can be the solution to this halting using - i have commented some of printf statements .

Waiting for a reply

Regards

  • 0
    TI__Expert 4125 points

    One idea: insure you do a device HW reset before reloading and running. If you run a program, interrupts are enabled. If you then just reload the program without resetting, an interrupt can go off (typically from the EMAC) before the software has been initialized, which can cause a crash (typically ending up in UTL_halt). In a real embedded product, each time there is a reset, the CPU is reset and interrupts are disabled. That is not happening when using the debugger unless you do i manually.

    Mark

  • 0 in reply to MarkGrosen
    Intellectual 900 points

    thanx 

    i will try that n get back at u ... 

     

  • 0 in reply to MarkGrosen
    Intellectual 900 points

    hello mark

    I have found im facing the same pb in the NOR flash boot mode ....

    its like i power up the board , n if it doesnt perform i repower the board again ... i repeat the repowering step untill the board starts working ...

    i already reported this to ti ... but till now they have not replied .... 

    kindly send in more ideas ... as i really need to resolve this issue....

     

    Regards 

  • 0 in reply to MarkGrosen
    Intellectual 900 points

    hello Mark ....

    your idea was correct , if loading the code i  did a HW reset and issue resolved. 

    But im facing the same pb with Nor flash boot mode , i did HW reset and the codes behaves in same manner sometimes it works and does successful communication but other times it get stuck after printing the two statements that it mentioned in my early post.

    Is it NOR boot mode issue , or is due to interrupts ?

    waiting for a reply

    regards

    Amna