• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 561 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.

AWR1843AOP: Secondary Bootloader

onur emre uygun
Prodigy 120 points
Part Number: AWR1843AOP
Other Parts Discussed in Thread: UNIFLASH, , AWR1843

Hello,

I wanted to run sbl for the AWR1843AOP board. I applied it, but then I could not connect the awr1843 chip with uniflash and ccs. First of all, I would like to tell you the steps I have taken.

First, I opened the C:\ti\mmwave_automotive_toolbox_3_6_0\labs\lab0012_can_sbl demo with ccs and made some adjustments.
* I wanted to provide the communication that will take place over the UART line in the demo over CAN, so I removed the UART communication and moved the communication that would take place over the UART line to the CAN line. and I checked. Of course, in order to control these processes, I provided myself a CAN converter and designed an interface.
* I specifically say CAN communication because I did not use CANFD. I made the necessary parameters and initial arrangements for this. I tested and did not encounter any errors.
* I used mmwave_sdk_03_06_00_00-LTS as sdk.
* After these steps were completed, I loaded the xwr18xx_ccsdebug.bin file with uniflash and debug the lab0012_can_sbl demo that I had edited with ccs. And I got it working.
* then I started to send the out_of_box_1843_aop.bin file with the interface I made and I sent the bin file successfully. However, the application I installed did not work. I tried to debug with CCS again, but without success. i got the following error

Cortex_R4_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x3c: (Error -1065 @ 0x0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.8.0.00235)
Cortex_R4_0: File Loader: Verification failed: Target failed to write 0x00000000
Cortex_R4_0: GEL: File: S:\TI_SPACE_YEDEK\can_sbl18xx_mss\Debug\can_sbl18xx_mss.xer4f: Load failed.

I can no longer connect to the 1843AOP chip. I tried 3 cards in this process. it was all garbage as well.

By the way, I would like to point out. Since I am using CAN communication, I corrected the offsets in the lab0012_can_sbl demo for CAN.

Where could I have gone wrong or is what I did completely wrong? How can I fix the error, please help.

  • 0
    TI__Guru*** 148514 points

    Hi,

    Unfortunately it is difficult to provide feedback based on this information.

    What is the SOP mode when you try to connect CCS?

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 120 points

    Hello,

    I already said above that I can debug with ccs. I don't have a problem with SOP mode. I find it strange that you asked. SOP mode is functional mode. First of all, my problem was that the application I installed via CAN with sbl did not work. I have tested that I have successfully installed it. then i couldn't connect to AWR1843AOP chip with ccs and uniflash. How can I reconnect with the cards? I need your opinions on how to find out what's wrong with sbl.

  • 0 in reply to onur emre uygun
    TI__Guru*** 148514 points

    Hi,

    Unfortunately our support team has limited experience with debugging SBL.

    I think there are several things to consider

    (1) Is the application image transferred correctly through CAN?

    (2) You could start testing with a simple application image such as ccs_debug.bin instead of the out_of_box_1843_aop.bin

    If the ccs_debug runs correctly you should be able to Connect CCS

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 120 points

    hi Cesar,

    we solved the errors, we also did sbl with CAN.
    i have a new problem. I did not understand the reason.

    1) The bit timing parameters below are the default values on the demo. When I run sbl with these values, the metaimage works after I load it with sbl, but when I change the baudrate, the imageFlasher and imageLoader operations are fine, then the metaimage does not work. I am sharing the baudrate values that I have changed below with you. you can check.

    a)
    ////////default parameters/////////////
    /* Configure the bit timing parameters. */
    mcanBitTimingParams.nomBrp = 0x2U;
    mcanBitTimingParams.nomPropSeg = 0x8U;
    mcanBitTimingParams.nomPseg1 = 0x6U;
    mcanBitTimingParams.nomPseg2 = 0x5U;
    mcanBitTimingParams.nomSjw = 0x1U;

    mcanBitTimingParams.dataBrp = 0x1U;
    mcanBitTimingParams.dataPropSeg = 0x2U;
    mcanBitTimingParams.dataPseg1 = 0x2U;
    mcanBitTimingParams.dataPseg2 = 0x3U;
    mcanBitTimingParams.dataSjw = 0x1U;


    B)
    ///////// 250 kbps baudrate values that I created ///////

    mcanBitTimingParams.nomBrp = 0x8U;
    mcanBitTimingParams.nomPropSeg = 0x8U;
    mcanBitTimingParams.nomPseg1 = 0x6U;
    mcanBitTimingParams.nomPseg2 = 0x5U;
    mcanBitTimingParams.nomSjw = 0x1U;

    mcanBitTimingParams.dataBrp = 0x8U;
    mcanBitTimingParams.dataPropSeg = 0x8U;
    mcanBitTimingParams.dataPseg1 = 0x6U;
    mcanBitTimingParams.dataPseg2 = 0x5U;
    mcanBitTimingParams.dataSjw = 0x1U;


    1.2) I tried the same operations for 125 kbps metaimage worked successfully. I need CAN working with 250 kbps. I would be glad if you can help with this.

    2) When I use the MCANParamInit() function with (metaimageUpdate == 1) instead of using it within the SBL_transportInit() function, it works properly at 250 kbps with the values I specified in part B. When the MCANParamInit() function is used in SBL_transportInit(), the imageFlasher and imageLoader operations are done properly, but the metaimage does not work. What causes this situation?


    I am sharing with you two different scenarios that I have encountered, and I need your help in these matters.

  • 0 in reply to onur emre uygun
    TI__Guru*** 148514 points

    Hi,

    It seems that there is some corruption in the CAN communication at 250 kbps.

    It is difficult for our support team to provided more information

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 120 points

    Hi cesar,

    I have successfully run the secondary bootloader. actually i fixed a bunch of bugs in the sbl demo and got it working. now I can successfully boot secondary bootloader with can and canfd.

    There are a few things I want to mention
    1) I could not get technical support from you on such an important issue or I was not directed. You should have provided support on an important issue such as secondary bootloader.

    2) In sbl demo, bootloader cannot be made with CAN or CANFD without uart connection, this is really ridiculous. That's not what the secondary bootloader is for. but i solved these situations and it works for its purpose. I think you should check the sbl demo again.

    3) I had a problem with can bautrate and I asked you about it. You say that the answer may be wrong. Why don't you specify what the error is? Shouldn't you be helping with this? Or you need to direct it to someone who knows.

    The replies to this post really pissed me off. thank you anyway.
    enjoy your work.