AM2634-Q1: Flash driver issues in MCAL_AM263x_00.09.00_03

Bruce(Shanghai) Liu

Part Number: AM2634-Q1

Hi team,

My customer found that in Fls_Brd_Nor_Qspi.c, both functions Fls_norBlankCheck()/Fls_norCompare() will run away. Cause there is a null pointer written in the function, which causes the program to run away after the flash is erased. As shown below, the value of readData_buf is always NULL.

over 1 year ago

0 Kowshik Gudimetla over 1 year ago

TI__Genius 15435 points

Hi Bruce,

Can I know what do you mean by "run away?" Is customer facing any issues while running the application or during the integration? If yes, please let us know the error or output.

Bruce(Shanghai) Liu said:
, which causes the program to run away after the flash is erased.

I don't think this is gonna happen because we also pass the length of block to be comapred or erased or written etc., So, I didn't get the problem the customer is facing. Please ask the customer to elaborate the query.

Thanks,
G Kowshik

0 Bruce(Shanghai) Liu over 1 year ago in reply to Kowshik Gudimetla

TI__Intellectual 1010 points

Hi Kowshik,

*readData_buf is NULL in the code, which means we will put the data read back from flash into the address of 0x0000. And if we use this address to store interrupts, and the program will run away.

0 Kowshik Gudimetla over 1 year ago in reply to Bruce(Shanghai) Liu

TI__Genius 15435 points

Hi bruce,

I'll get back on this by monday EOD.

Thanks

0 Kowshik Gudimetla over 1 year ago in reply to Bruce(Shanghai) Liu

TI__Genius 15435 points

Hi Bruce,

Your understanding on the initializing the readBuf pointer to NULL is slightly wrong. With the statment *readData_buf = NULL we are assigning the value of the 1st element to 0, but not the address of the readData_buf to NULL. Hence the program will work correctly. The buffer is going to be allocated in the program stack memory not in the 0x00 location as you mentioned. You can compile the program and look at the map file which gives you the location of this buffer.

Thanks