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.

Problem with update

Other Parts Discussed in Thread: SYSBIOS

Hello everybody,


I have a problem generated by updates.

In fact, I had created a little program of booting which was a mix of a traditionnal boot and a simple ethercat programm that implement fsoe for downloading and flashing a new code in my dsp. I work on a sitara arm3359.

I had created this program a long time ago: I have used sdk 1.1.0.4 + xdctools 3.25.5.94 + sys/bios 6.33.5.46. This program was a success !

Now, I want to update my software whith the last souces: sdk 1.1.0.8 + xdctools 3.30.6.67_core + sys/bios 6.41.4.54. I have made all the necessary modifications in all the files. When I launch this program in DEBUG everything is all right. Then I create the good .bin and i flash it at the bootloader place.... But nothing work ! I tried to see what happens using a uart debug but what i see is that the program does not start at all !!! I have checked the .bin generated, the memory flashing... everything seems correct !

Is anyone have an idea ? I think it's a problem due to xdctools and sysbios but i don't know what...

Tha nks a lot for your help

Laurence

  • Hi,

    I will forward this to the ISDK team.

  • Hi,

    From what I understand, you have a new bootloader here. Is the bootloader starting alright? if yes, is the control transferred to the application entry point correctly?

    Regards,
    Vinesh
  • Hello,

    In fact my problem is that my custom bootloader (which is a mix between the traditional boot + an simple ethercat application that implements ethercat) doesn't start at all when i load it in the sitara flash.

    When I debug it in RAM there's no problem but whan i make a .bin and flash into the sitara memory nothing starts (at the beginning of the main, the bootloader writes on the uart and i don't see anything).

    Regards,

    Laurence

  • Hello Vinesh,

    I can give you some details to help you to undesrtand my problem.

    In fact my custombootloader is a mix between the traditionnal boot program and the ethercat program provided by texas.

    This custom bootloader was working good with the sysbios 6.33.5.46 + xdctools 3.25.5.94.

    I wanted to make the good upadte: sysbios 6.41.4.54 + xdctools 3.60.6.67_core.

    I made all the necessary updates.

    Then  I try my program in DEBUG: OK.

    Then I try to flash this bootloader: NOK.

    Thanks to my serial uart, I managed to focus on the function that put problem:  "tsk1 = Task_create (task1, &taskParams, NULL)".

    This function seems to reset evrything !!!!

    I also made the foolowing verification : the traditionnal boot program and the ethercat apllication program are OK with this sysbios.

    Do you have an idea to solve my problem ?

    Thanks a lot

    Laurence

  • Laurence,

    We have seen that while updating the SYS/Bios versions, usually the binary size grows(text, data etc.). The issue here could be that the Bootloader/app placement in the flash is overlapping? You can verify these by comparing the map files of the bootloader and app.

    Regards,
    Vinesh

  • Hello Vanesh,

    I had already noticed that the size were growing but everything seems all riht in my map file (no overlap).

    I wiil send you the map file tomorrow (I'm out of my office today) but i don't think my problem is a mapping problem.

    Do you have any other ideea ?

    Regards,

    Laurence

  • Hello Vanesh,

     

    I send you my map file to verify that there's no overlapping problem in my bootloader.

    Do you have any other idea that makes the function Task_create never ending ?

    Regards,

     

    LaurenceNewBootEthercatMiniMap.txt

  • Hi Laurence,

    Did you do a comparison on the map files of working/non-working application?

    Regards,
    Vinesh

  • Of course I did it !
    And what I saw is that the function "ti_sysbios_knl_Task_create" that refers to the Task_create function does not exist in the working project. In fact, the two librairies are completely different but I don't think that it is my problem...
    To summarize my situation: when I call the function Task_create nothing work in my project; the uart log, even the ones before the call to the function, don't appear... But if I comment the call to this function, everything is all right....
    An idea ?

    Thanks a lot,

    Laurence
  • That's weird. Seems the issue is with Task_create not defined in the binary. Will have to loop in CCS/SYSBios experts for help.

    Regards,
    Vinesh
  • Can you transfer them this post please ?
    Thanks,

    Laurence
  • Vinesh,

    In fact it seems to be a size issue as you said first. Instead of creating task1 (which is the task of ethercat that created PDITask and Sync0Task) i have created a task that do noting (sjut a while instead) and then the program functions !
    So I think that there's a problem of overlapping but I don't know where.
    So I try to look into the map file and see the adress where are stocked somme function. First I searched the first function called in the main program of boot : "BlPlatformConfig" and I can't find this function in the map file. Even in the map file of a well working function. ... I don't undersatnd how the map file function: I can find some functions but not ALL the function of my program !!!
    Can you explain me how it is possible ?
    Or do you have a documentation on that ?
    Do you have any idea to point out my size proble ?

    Thanks

    LAurence
  • Hello,

    Nobody can help me please ?

    Laurence
  • Your issue has been sent for investigation by the SYS/BIOS team. However there are holidays now in the USA and most people are on vacation. Response may be delayed after Monday.

  • Hello Vinesh,

    As I said you in my last post I think that there is un problem in my mapping but I don't know what is the problem.

    I have already send you my map file: can you have a look at it to see if you can find a problem ?

    Thanks a lot.

    Regards,

    Laurence

  • Hi Vinesh,

    Sorry for the delayed response.

    I looked at your .map file and it seems like the Task_create function is being pulled in from the ethercat_pea8fnv library rather than the sysbios library (line 471 of the map file). Can you please post a screen shot of the linker libraries in your project? Additionally, can you post the link line that is on the console when you compile the project?

    Thanks,
    -- Emmanuel
  • Hello Emmanuel,

    Thanks for your answer !

    I was about to be very anxious about my unsolvable problem...

    I join you the 2 things you asked me...

    Do you have any idea of the problem ?

    Thanks a lot

    Laurence