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.

CC3301: Trouble getting started with SDK 1.3 / LP-AM243 (with secure chip)

Part Number: CC3301
Other Parts Discussed in Thread: LP-AM243,

Hi 

I have been up and running with the 01.02 SDK and the LP-AM243 with the GP Chip.

I have received 2 new boards from you (one seems defect - this is discussed in another thread with the ARM team)

Again being new to this Sitara board / toolchain I am strictly bound to the getting guides and unfortunately it seems like your CC3301 getting started docs aren't addressing the LP-AM243 with the secure chip.

I have now succeeded flashing the boot image with the .hs_fs. extension

 

Then opening the wifi ble provisioning example and running the load_dmsc_hsfs.js to enable JTAG

As you can see I end up with "Happy debugging!!" -so it should be ready to go now - but as you can see some file(s) are missing ? 

And if I try to debug now - it seems normal at first - project being build - XDS110 is being used to transfer the build - but it never begin like normal with the "run to main" - it is kind of stuck in all the pre init.

I hope you can give me a hint on what I am doing wrong here ?

Once again - I am up and running with SDK 01.02 and the old "GP" LP-AM243. 

Kind regards

Thomas

  • are you running SDK1.2 or SDK1.3 ?

    SDK1.3 (with AM243 8.5) supports the secure interface. 

  • Hi Kobi

    I am running 1.3 with the 8.5 AM243 SDK with the new boards that came with the secure chip onboard. 

    And again I figured out what hs_fs image files to use - this is unfortunately not explained in the getting stated docs.

    And I figured out that I had to use load_dmsc_hsfs.js to enable JTAG - when dealing with a secure board.

    The reason that I mention the 1.2 SDK with the 8.0 AM243 SDK and non secure chip - is that this works when I follow your getting started doc.

    So what I really need (I think) is an updated getting started doc that clearly shows how to get up and running with 1.3 / 8.5 + the secure board.

    As you can see from the initial post I have come a long way setting up the whole stuff - it just don't "autorun to main" when hitting debug.

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    A new discovery - Setting the dipswitches to QSPI Boot mode - here is what is printed to a terminal "some test have failed!" 

    Again it makes me doubt that the images I am flashing to the board are correct? 

    Kind regards 

    Thomas

  • hi Thomas,

    does the flash programming works for you (from the secured_programming folder)?

    the “Run from CCS” was not updated as you mention. i just tried it now and couldn’t make it work with No Boot Mode (did it worked when you used the hsfs hs script?), however when using the QSPI mode (same as running from flash), i was able to run my code without running any script (just lanuch target config, connect and load the image or use the “Debug” button).

    note that the links in the getting started still point to am243x 8.00.00.22. we will provide an updated version of the document. 

  • Hi Kobi

    does the flash programming works for you (from the secured_programming folder)?  Yes - I guess so - this is what the first picture shows in the initial post - from the screen dump - you can see exactly what files I have been using 


    did it worked when you used the hsfs hs script? Well - again as mentioned in the initial post - the script seems to be executed correct and it returns "happy debugging!" so I should be go to go from there. 

    It would be very nice if you would update the SDK package - so the whole "out of the box experience" match SDK 1.2 and the non secure boards - Thanks!

    -----------------------------------------------------------------------------------------------------------------------------

    Normally i am using the ble wifi provisioning example.

    I have also tried the network_terminal_example project with no boot mode setting - hit debug and it actually "autorun to main" when I push RUN it gets stuck in this line. (see picture)

     

    So again it would be nice if you would revisit the whole SDK 1.3 version and make sure that it works "out of the box" because engineers like me that only has a focus on evaluating the WiFi part.

    Thanks!

    Kind regards

    Thomas

  • You can use the secured_programming/ to flash the program too and then run it from the flash (i.e. it will run after reset).

    I'm not sure what is the problem with the network terminal that you mentioned - It just worked for me.

    Have you changed anything in the code? syscfg?

    Did you try using CCS to load The BLE Provisioning example? Is it getting stuck at the same place? (if not please compare syscfg of the 2 examples). 

    We will update the documentation but till then you can refer to the AM243x guides (we simply summaries them), specifically.:

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/08_05_00_24/exports/docs/api_guide_am243x/GETTING_STARTED_FLASH.html

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/08_05_00_24/exports/docs/api_guide_am243x/CCS_LAUNCH_PAGE.html

    in their getting started guide

    Unfortunately we found the hsfs issue at the last moment just before releasing this version and the required move to the new SDK was too quick. 

  • Hi Kobi

    I have another thread here at the e2e forum - regarding a similiar sitara board that has seemed faulty from the beginning
    https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1227718/lp-am243-board-seems-bricked-or-am-i-doing-something-wrong/4650776#4650776

    Erik from the Arm team has guided me to do a flash check and from that test it is concluded that the board has an flash chip error.

    I tried the same test on flash test on the board setup that we have been discussing and it also comes out with a an error when running the flash chip test.

    So maybe this explain some of the errors I experience.  I will write write to Erik from the ARM team to tell about this board - maybe it is a general issue with the actual lot of LP Board  

    We have decided to await SDK fix and new boards before spending more time on this right now.

    Kind regards

    Thomas