LAUNCHXL-F28377S: F2837xS and F2807x Tools Support

Hey guys,

I have the same problem. I get an blank error when i perform dfu and earse command.

Is there a solution.

Thanks Alex

I was attempting a DFU. I know what debug means, i was asking how to put the launch pad into debug mode while still having it in sci boot mode The only connection i have to the launch pad is the mirco usb. Will this work as a channel for both jtag-debug as well as the serial line to send the the application to the flash kernal?  Please provide the dip switch positions as well as any emuboot registers required to run the launch pad in emulator/sci boot mode. It seems several people are having the exact same problem. Please confirm that this process is possible by replicating it on the hardware on your side.

Russell

Alex,

Please see if below helps:

1) Could you search for "If the Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector, xx) does not wait for the erase operation completion, how do we know whether the erase operation succeeded or not?" in the Flash API wiki at processors.wiki.ti.com/.../C2000_Flash_FAQ.

2) Also search for "What are the common debug tips that we can consider when Flash API fails to erase or program?".  It may help debug.

Thanks and regards,

Vamsi

Bravo! It works for me as well. Thanks Alex! Now help Alex with his Issue!

Alex, Rostislav,

Great catch! Good debugging! I apologize the flash kernel for the single core F2837xS with dual banks is not so robust. It did not include this feature/enhancement. I have filed a bug to fix this.

Could you both kindly post your solution here for us and for others? Please post code snippets of the code you changed to implement this fix.

Thank you,
sal

ello Sal Prezzino,

here are my patch for your bootloader.

I just remove the bank1 initial because we want write to bank0.

It works for blinky programm, but when i try to download my program

it dont works.

I get an PROGRAMM ERROR:

Downloading MyProgramm.a00 to device...

ADRESSE: 82000  BLOCKSIZE: 1021

ADRESSE: 80000  BLOCKSIZE: 2

ADRESSE: 80002  BLOCKSIZE: 3235

ADRESSE: 82400  BLOCKSIZE: 7168

ADRESSE: 84000  BLOCKSIZE: 4298

ADRESSE: 90000  BLOCKSIZE: 1418

Application load successful!

Done waiting for application to download and boot... input and output successfully flushed

SUCCESS of Command

ERROR Status: PROGRAM_ERROR

ERROR Address: 0x07c88

My linker file dont use bank1.

Can you explain me why i must manage bank1.

Or can you give me an fix for the bootloader to manage the banks.

Alex

From c68b78dc57557a6ac2c9ef1b58c1f843194798c1 Mon Sep 17 00:00:00 2001
From: alexn <aniebling@mibtec.de>
Date: Mon, 16 Jul 2018 13:59:04 +0200
Subject: dont initial bank1. now we dont get an blank error. blinky works.

---
 F2837xS_sci_flash_kernel.c | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/F2837xS_sci_flash_kernel.c b/F2837xS_sci_flash_kernel.c
index 31bc764..ec058d2 100644
--- a/F2837xS_sci_flash_kernel.c
+++ b/F2837xS_sci_flash_kernel.c
@@ -129,7 +129,7 @@ uint32_t main(void)
     //
     // Initialize the Flash.
     //
-    InitFlash_Bank1();
+    //InitFlash_Bank1();
     InitFlash_Bank0();
     Init_Flash_Sectors();
 
@@ -157,7 +157,7 @@ void Init_Flash_Sectors(void)
 {
     EALLOW;
     Flash0EccRegs.ECC_ENABLE.bit.ENABLE = 0x0;
-    Flash1EccRegs.ECC_ENABLE.bit.ENABLE = 0x0;
+    //Flash1EccRegs.ECC_ENABLE.bit.ENABLE = 0x0;
 
     Fapi_StatusType oReturnCheck;
     oReturnCheck = Fapi_initializeAPI(F021_CPU0_W0_BASE_ADDRESS, 150);
@@ -165,25 +165,25 @@ void Init_Flash_Sectors(void)
     {
         Example_Error(oReturnCheck);
     }
-    oReturnCheck = Fapi_initializeAPI(F021_CPU0_W1_BASE_ADDRESS, 150);
-    if(oReturnCheck != Fapi_Status_Success)
-    {
-        Example_Error(oReturnCheck);
-    }
+    //oReturnCheck = Fapi_initializeAPI(F021_CPU0_W1_BASE_ADDRESS, 150);
+    //if(oReturnCheck != Fapi_Status_Success)
+    //{
+    //    Example_Error(oReturnCheck);
+    //}
 
     oReturnCheck = Fapi_setActiveFlashBank(Fapi_FlashBank0);
     if(oReturnCheck != Fapi_Status_Success)
     {
         Example_Error(oReturnCheck);
     }
-    oReturnCheck = Fapi_setActiveFlashBank(Fapi_FlashBank1);
-    if(oReturnCheck != Fapi_Status_Success)
-    {
-        Example_Error(oReturnCheck);
-    }
+    //oReturnCheck = Fapi_setActiveFlashBank(Fapi_FlashBank1);
+    //if(oReturnCheck != Fapi_Status_Success)
+    //{
+    //    Example_Error(oReturnCheck);
+    //}
 
     Flash0EccRegs.ECC_ENABLE.bit.ENABLE = 0xA;
-    Flash1EccRegs.ECC_ENABLE.bit.ENABLE = 0xA;
+    //Flash1EccRegs.ECC_ENABLE.bit.ENABLE = 0xA;
     EDIS;
 }
 
-- 
cgit v0.11.0

Alex,

If you don't want to erase/program/verify Bank1, then you don't need to call Fapi_initializeAPI() and Fapi_setActiveFlashBank() for Bank1.  If you are not using Bank1 in your linker command file to allocate any code/data to it, then I agree that you don't need to initialize it's read interface as well - meaning, you don't need to call InitFlash() for Bank1.  

A) Can you check whether the Flash pump semaphore is allocated for FMC0 or not, when Flash program operation is failing for Bank0?

B) What is the exact error that you get from program function call? 

C) Did you check FMSTAT after the failure? If yes, what is the value of FMSTAT - that would help us debug further.

Thanks and regards,

Vamsi

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

P.S: Below content is just for FYI (looks like you already know this stuff) - but just in case.

1) When application wants to perform Bank0 erase/program/verify operations, below functions should be called to initialize FMC0 and Bank0 (please note that parameters are related to Bank0/FMC0).

   //

   //Give pump ownership to FMC0

   //

   PUMPREQUEST = 0x5A5A0002;

   //

   // This function is required to initialize the Flash API based on System

   // frequency before any other Flash API operation can be performed on Bank0.

   // Note that the FMC0 register base address is passed as the parameter

   //

   oReturnCheck = Fapi_initializeAPI(F021_CPU0_W0_BASE_ADDRESS, Freq);

   if(oReturnCheck != Fapi_Status_Success)

   {

       //

       // Check Flash API documentation for possible errors

       //

       Example_Error(oReturnCheck);

   }

   //

   // Fapi_setActiveFlashBank function sets the Flash bank0 and FMC0 for

   // further Flash operations to be performed on Bank0.

   // Note that the parameter passed is Fapi_FlashBank0 since FMC0 register

   // base address is passed to Fapi_initializeAPI()

   //

   oReturnCheck = Fapi_setActiveFlashBank(Fapi_FlashBank0);

   if(oReturnCheck != Fapi_Status_Success)

   {

       //

       // Check Flash API documentation for possible errors

       //

       Example_Error(oReturnCheck);

   }

2) When application wants to perform Bank1 erase/program/verify operations, below functions should be called to initialize FMC1 and Bank1 (please note that parameters are related to Bank1/FMC1).

   //

   // Give pump ownership to FMC1

   //

   PUMPREQUEST = 0x5A5A0001;

   //

   // This function is required to initialize the Flash API based on System

   // frequency before any other Flash API operation can be performed on Bank1.

   // Note that the FMC1 register base address is passed as the parameter

   //

   oReturnCheck = Fapi_initializeAPI(F021_CPU0_W1_BASE_ADDRESS, Freq);

   if(oReturnCheck != Fapi_Status_Success)

   {

       //

       // Check Flash API documentation for possible errors

       //

       Example_Error(oReturnCheck);

   }

   //

   // Fapi_setActiveFlashBank function sets the Flash bank1 and FMC1 for

   // further Flash operations to be performed on the bank1.

   // Note that the parameter passed is Fapi_FlashBank1 since FMC1 register

   // base address is passed to Fapi_initializeAPI()

   //

   oReturnCheck = Fapi_setActiveFlashBank(Fapi_FlashBank1);

   if(oReturnCheck != Fapi_Status_Success)

   {

       //

       // Check Flash API documentation for possible errors

       //

       Example_Error(oReturnCheck);

   }

3) Please note: Since there are two FMCs for a single core in F28377S, above functions must be called whenever the target bank is changed.  Only one of the bank can be active for erase/program/verify operations.  Hence, whenever the application wants to switch the target bank for Flash operations, above functions for respective bank should be called before performing Flash operations on that bank.  Note that Flash wait-states should be configured before calling these functions.

4) Coming to Flash read interface configuration: You might have noticed the functions InitFlash_Bank0() and InitFlash_Bank1() - these can be used to initialize Bank0 and Bank1 respectively (wait-states can be changed based on your application frequency).  These should be called before using any Flash API functions.  And both of them can be executed irrespective of which bank you are targeting for erase/program/verify.

//
// Call Flash Initialization to setup flash waitstates, fallback power mode, ECC etc.
// This function must reside in RAM
//
InitFlash_Bank0();
InitFlash_Bank1();

Alex,

Could you update on the status of your debug?

Thanks and regards,
Vamsi