Jive

Hi Steven,

I had a look but I cannot find the task switch trace support you are speaking about, can you point me to where you saw that?

I've added

configCHECK_FOR_STACK_OVERFLOW in FreeRTOSConfig.h but I've a stupid error at the moment I'm trying to figure out:

StackMacros.h:107: error: expected identifier or ‘(’ before ‘{’ token

thanks

William

Hi Steven,

I've corrected the compilation error and run with configCHECK_FOR_STACK_OVERFLOW = 1. But the stack do not seem to overflow

let me know if you saw more debug options

Thanks,

William

Hi Steven,

I did implement the debugging function as you sudgested (thanks) .

there is few more logs that may tell you something but I cannot see to much in it. I've highlighted in red what I find suspicious:

COREB: end setup LED                                                           
COREB: handler declared                                                        
COREB: Initialise New TCB:NewTCB address: 3d01000                              
COREB: TopofStask: 0, pxTopOfStack = 3d0263c                                   
COREB: pxTaskCode =3c033a0, pvParameters = 0                                   
COREB: returned pxNewTCB->pxTopOfStack = 3d02588                               
COREB: task created:                                                           
COREB: top of stack: 3d02588                                                   
COREB: GenericListItem: 0                                                      
COREB: Event ListItem: 9                                                       
COREB: Priority: 1                                                             
COREB: start of stack: 3d02000                                                 
COREB: Task Name: BootTas                                                      
COREB: TCB number: 0                                                           
COREB: Task Tag: 0                                                             
COREB: Add the idle task at the lowest priority                                
COREB: Initialise New TCB:NewTCB address: 3d03000                              
COREB: TopofStask: 0, pxTopOfStack = 3d0431c                                   
COREB: pxTaskCode =3c0295c, pvParameters = 0                                   
COREB: returned pxNewTCB->pxTopOfStack = 3d04268                               
COREB: task created:                                                           
COREB: top of stack: 3d04268                                                   
COREB: GenericListItem: 0                                                      
COREB: Event ListItem: a                                               <--------------- this is not a number, not sure it is normal        
COREB: Priority: 0                                                             
COREB: start of stack: 3d04000                                                 
COREB: Task Name: IDLE                                                         
COREB: TCB number: 1                                                           
COREB: Task Tag: 0                                                             
COREB: end Add the idle task at the lowest priority                            
COREB: if xReturn == 1, and xReturn = 1                                        
COREB: before disable interupt                                                 
COREB: after disable interupt                                                  
COREB: before  xPortStartScheduler                     <---------------- below it print this name in the task switch out debug at for the val:                                                                                                           pxCurrentTCB->pcTaskName                                   
COREB: start xPortStartScheduler fn before set core timer                      
COREB: after ContextSwitch interupt flag                                       
COREB: before prvSetupTimerInterrupt                                           
COREB: after prvSetupTimerInterupt                                             
COREB: Task Switch context called                                              
COREB: The scheduler is running                                                
COREB: trace switched out TCB:ff700bf8                                         
COREB: name of switch out task:efore  xPortStartScheduler     <-------------- there is no name associated, instead it provide a message from one of my                                                                                                                              coreb_msg not sure why                 
                                                                               
COREB: before Task first check for stack overflow                              
COREB: Task first check for stack overflow called                              
COREB: Task second check for stack overflow called                             
COREB: before call get owner of next entry                                     
COREB: get owner of next entry:                                                
COREB: current TCB 3d01000                                                     
COREB: pxReadyTasksLists[ uxTopReadyPriority ] = 1                             
COREB: TCB content:                                                            
COREB: top of stack: 3d02588                                                   
COREB: GenericListItem: 0                                                      
COREB: Event ListItem: 9                                                       
COREB: Priority: 1                                                             
COREB: start of stack: 3d02000                                                 
COREB: Task Name: BootTas                                                      
COREB: TCB number: 0                                                           
COREB: Task Tag: 0                                                             
COREB: trace switched in:BootTas                                                 <------------------ switch in BottTask as it supose to                                                       
COREB: write trace to buffer                                                   
COREB: task increment tick: 1                                                  
COREB: end of app init                                                         
COREB: execption 2b addr ff700be4                                              
COREB: coreb dump stack                                                        
COREB: found fp: ff700b64

Best Regards,

William

Hi Steven,

I wish you an happy new year.

it has been a while with the end of the year break. I went back to try to resolve this issue, what do you think of the trace log in the last post?

As well I've noticed that instead to jump to the address pxTaskCode =3c0342c for the vBootTask it jump to app_init() function at address 03c0592c

doing 03c0592c - 3c0342c = 2500

I don't think this number happened by chance, which mean something offset the memory of 0x2500

Do you know what could correspond to that hex amount? is the memory block from icc maloc function is equal to this amount? in decimal, this represent 9472 bytes almost 10Kb

as well I've try to put some debugging in the assembly code as follow:

* Manual context switch.  The first thing we do is save the registers so we   

*/

/*  This function is also the ISR for interrupt 2 */

.section .text

_vContextSwitch:

_vContextSwitch.end:

But I get a linking error when I compile a linking error probably due to long call:

/home/william/Development_new/Music_Recognition/code/uCLinux/uclinux-dist/user/blkfin-apps/icc_utils/example/tested_by_AD/Source/portable/ADI_VDSP/Blackfin/bfin_isr.s:44: relocation truncated to fit: R_BFIN_PCREL24 against symbol `coreb_msg' defined in .text section in ../../icc_core/icc

make: *** [test_ad1836_driver] Error 1

Could you tell me what I did wrong as getting the assembler debug working could help debug further

William

Hi Steven,

In addition to the previous post, I found part of the problem which come from a translation from VDSP assembler to bare metal assembler. unfortunatly, excepted few examples in blackfin doc I cannot find a good manual about the assembler used, especially about how to setup interupts.

I'm trying to immitate your file  coreb_start.S by replacing the code with

ENTRY(_vContextSwitch):

.....

ENDPROC(_vContextSwitch)

instead of:

_vContextSwitch:

.....

_vContextSwitch.end:

what happened when _vContextSwitch.end: was called, it was not returning from the interupt, instead it did continue to the next assembly function: _vTickISR which if preemption is selected call _vTaskSwitchContext as well which explain why initially it was called twice.

Maybe that 's it but I need to start and end properly the function to test it. For the moment I got errors:

" syntax error. Input text was entry."

Thanks William

Hi Steven,

by separating the 2 interupt in different files I managed to make it run, this time it call few time the switch context before to go bake to the problem of jumping to app_init function

COREB: end of app init

......

Hi Steven,

actually, it is the same, I test it again with the flag pre-emptive off (as it was in previous test to identify the issue) and it is the same as before:

.....

COREB: execption 26 addr 3d027f4

in fact looking at the dump file I can see that despite I put it in 2 files they follow each other and thus vContextSwitch do not return as before and continue to the next address which is _vTickISR

Hi Steven,

Actually, I found a get around by making those iterupts in C instead of assembler. this resolve the problem of running out from the code but it still not work corectly. There is no crash anymore but the interupt do not seem to react properlly, the new intrupt functions look like:

void __attribute__((interrupt_handler)) vTickISR(void);

void __attribute__((interrupt_handler)) vContextSwitch(void);

void __attribute__((interrupt_handler)) vContextSwitch(void)

{

    coreb_msg("start vcontext switch interupt \n");

    vTaskSwitchContext();

    coreb_msg("end vcontext switch interupt \n");

}

void __attribute__((interrupt_handler)) vTickISR(void)

{

    vTaskIncrementTick();

}

do I miss something in it?

their setup are:

void prvSetupTimerInterrupt( void )

{

    int scale = 134;

    int counter = 100000;

//    *pTCNTL   = 1;                                   // Turn on timer, TMPWR 

    *tcntl = 0x01;

//      *pTSCALE  = scale;                               // Load scale         

    *tscale = scale;

   /* Interrupts are disabled when this is called so the timer can be started 

        here. */

//      *pTCNTL   = 0x7;                                 // Start Timer and set\

Auto-reload                                                                   

      tcntl = 0x07;

}

and:

portBASE_TYPE xPortStartScheduler( )

{

        char tmp[220];

    int i;

    coreb_msg("start xPortStartScheduler fn before set core timer\n");

    /* Setup core timer to generate the RTOS tick. */

    //register_handler_ex (ik_ivg14, (ex_handler_fn)vContextSwitch, EX_INT_\

ENABLE);                                                                       

        bfin_write_EVT14(vContextSwitch);

        asm volatile ("cli %0; bitset (%0, 14); sti %0; csync;": "+d"(i));

        coreb_msg("after ContextSwitch interupt flag\n");

        coreb_msg("before prvSetupTimerInterrupt\n");

    prvSetupTimerInterrupt();

....

}

is there is something I missed?

Ok finally after all this time, I resolved the issue. Not only the assembler code was falty but in addition the hook function from the context loader was not trigger neither the Tag of the function was indicated. I've added it all up miself in the FreeRTOS code and it finally work

Thank Steven for your support over all that and especially for fixing memory issues.

Best Regards,

William

Hi Steven,

well in bfin_isr.s located in Source/portable/ADI_VDSP/Blackfin :

.text

.global _vContextSwitch;                                                       

_vContextSwitch:

    _portSAVE_CONTEXT;                                                         

        /* Call the standard scheduler context switch function. */

        LINK 0x0;                                                              

        SP += 12;                                                              

        call.X _vTaskSwitchContext;                                            

    UNLINK;                                                                

    _portRESTORE_CONTEXT;                                                      

_vContextSwitch.end:

with _portRESTORE_CONTEXT which is a MACRO which finish with:

.....

that you can find in the file

context_sl_asm.asm  of the same folder

RTI do not work and the code continue to run to the next assembly function vTickISR then tot he next code in memory which is app_init function.

maybe the compiler does not handle all the conversion of .asm and I should have change the extension to .s or it was a problem with the MACRO.

Hope you had good vacation,

Let me know if you know where exactly it come from just by curiosity.

best regards

William

Hi Steven,

maybe, I thought that adding assembler-with-cpp would have done the trick. I did have try to change to .s but didn't remove the flag assembler-with-cpp so maybe it is why.

Thanks

William