Compiler/TDA2EX17EVM: sd startup problem

Hi,

Supplement to the above question.Although RTOS can be booted from SD, I compare the current boot date with the previous one and find the following differences：

1、It will prompt when starting "SBL Initial Config Failed ",there was no such prompt before.

2、When the execution reaches "Putting MPU in Retention...", the waiting time is very long .

3、The following error message is displayed midway

[IPU1-0] 11.958366 s:
[IPU1-0] 11.958610 s: i2cMdSubmitChan: i2c transfer Timeout IRQ not received
[IPU1-0] 11.960013 s: src/bsp_deviceI2c.c @ Line 667:
[IPU1-0] 11.960074 s: I2C0: DEV 0x51: ERROR !!!
[IPU1-0] 11.960165 s: src/bsp_deviceI2c.c @ Line 689:
[IPU1-0] 11.960257 s: I2C0: Error timeout 5001 ms!!!
[IPU1-0] 16.964497 s:
[IPU1-0] 16.964741 s: i2cMdSubmitChan: i2c transfer Timeout IRQ not received
[IPU1-0] 16.966144 s: src/bsp_deviceI2c.c @ Line 478:
[IPU1-0] 16.966205 s: I2C0: DEV 0x51: RD ERROR !!!
[IPU1-0] 16.966296 s: src/bsp_deviceI2c.c @ Line 504:
[IPU1-0] 16.966388 s: I2C0: Error timeout 5001 ms!!!
[IPU1-0] 16.966479 s: src/bsp_boardTda2ex.c @ Line 769:
[IPU1-0] 16.966540 s: EEPROM read failed!!

There was no such prompt before.

I feel very strange, I just run the driver I added in the Linux system. For details, see the attached log.Then, I cut off the power and restarted the system.

There was no information on the serial port, the rom could not detect the SD card or did not recognize the SD card, but I could start by replacing the image in the SD card with MOL of RTOS.

Hi,

Can you try with the new SD card?

Is it working in the RTOS? If it is working, can you mention the Use-case name? if it's is a custom use-case then mention the chain you have created.

Thanks

Gaviraju

Hi,

I have made a new sd card, but still can’t start, there is no information in the serial port.I use the "4CH VIP LVDS capture + SGX MOSAIC + DISPLAY" use case, which can be seen in the log.Does the information I provided above help you at all?

Now, after this phenomenon occurs, although atos can be booted from the SD card, an error message also appears during its startup, such as:In my first additional question.My tracking program is not successful when executing SBLUtilsConfigAllVoltageRails(oppId).

Hi,

Does anyone help me answer this question? I can’t burn and start the tda2ex17 board with the sd card now.I don't know how to check.

Help me，please

Hi Gaviraju,

During this time, I carefully check the hardware electrical signals.As shown below

Have the following problems:

1、Measure I2C1_SCL and  I2C1_SDA voltages are both low,Normally it should be high.This causes the i2c command to read the LP87332DRHDRQ1 register after the sbl is started to fail.

2、I don't know what the rvs pin does.No description of this pin was found in trm.The H_VPP voltage measured on my evm board is zero.Indicates that there is no work. Will this have any effect?

3、I’ve been posting this thread for five days and haven’t got a definitive answer yet.This makes me unable to continue to develop on the linux system, and the rots system always prompts i2c read and write errors.

I'm about to collapse, I need your help very much now.

Thank you very much！

Hi,

Is this issue observed on more than one board?

Regards,
Vishal

Hi,

I am a little disappointed. I have listed so many descriptions about this problem and the phenomenon of my comparison test.

I only hope to come to you such a simple question.

I just bought the tda2e-17 development board. This development board is too expensive, so there is only one.

Now I can’t read and write the secondary boot program MLO from the sd card, and there is no other memory to burn the firmware,

so I can’t use this The linux system is running on the board. This problem has been bothering me for a week. I have listed the logs

and reasons before and after the problem occurred in the front of this thread. Please read carefully the description of this problem

that I have posted before and the situation of my own comparison test with RTOS. I hope that the expert will give an accurate solution.

Thank you

Hi,

I thought this issue was seen with your custom board and not TI EVM.
That's why I asked how many boards show this issue.

Let me check with the team and get back if we have seen such issue with TI EVM.

Regards,
Vishal

Hi  vishal

Please believe that all the above problem descriptions and phenomena occurred on the development board of tda2ex17 that you officially purchased.

All the questions and phenomena about me before this post are now summarized below for the reference of TI experts:

1、Before the sd can start the linux system normally, when I put the rtos system image in the sd card and start the development board, the following information will not be prompted:

1）In the MLO boot phase of rtos com port cmd prompt ："SBL Initial Config Failed "

2）When the execution reaches "Putting MPU in Retention...", the waiting time is very long .

3）After the appImage is loaded, an error message related to i2c1 will also be prompted：

[IPU1-0] 11.958366 s: 
[IPU1-0] 11.958610 s: i2cMdSubmitChan: i2c transfer Timeout IRQ not received
[IPU1-0] 11.960013 s: src/bsp_deviceI2c.c @ Line 667: 
[IPU1-0] 11.960074 s: I2C0: DEV 0x51: ERROR !!! 
[IPU1-0] 11.960165 s: src/bsp_deviceI2c.c @ Line 689: 
[IPU1-0] 11.960257 s: I2C0: Error timeout 5001 ms!!!
[IPU1-0] 16.964497 s: 
[IPU1-0] 16.964741 s: i2cMdSubmitChan: i2c transfer Timeout IRQ not received
[IPU1-0] 16.966144 s: src/bsp_deviceI2c.c @ Line 478: 
[IPU1-0] 16.966205 s: I2C0: DEV 0x51: RD ERROR !!!
[IPU1-0] 16.966296 s: src/bsp_deviceI2c.c @ Line 504: 
[IPU1-0] 16.966388 s: I2C0: Error timeout 5001 ms!!!
[IPU1-0] 16.966479 s: src/bsp_boardTda2ex.c @ Line 769: 
[IPU1-0] 16.966540 s: EEPROM read failed!!

The above three error messages are all started when the sd cannot read the Linux system boot image MLO.Before this, there was no error message above.

Measure I2C1_SCL and  I2C1_SDA voltages are both low,Normally it should be high.This causes the i2c command to read the LP87332DRHDRQ1 register after the sbl is started to fail.

2、The difference between rtos mirror and linux mirror

1）The rtos image can be placed in the SD card to drive the MLO normally and boot the system to load the appImage, except for the error message mentioned above, everything else is normal。

2）Put the linux image in the SD, keep the SD on and start the settings, and there is no prompt message on the debug serial port. There are two possibilities. One is that RBL cannot read

the MLO from the SD card, but this is obviously not true, because the same startup Configuration, rtos mirror can be started.The only difference between the MLO of rtos and linux is

the mirror link, but both are loaded by RBL to the chip's internal ram at 0x4030 0000.

4、my question：

1）I don't know what the rvs pin does.No description of this pin was found in trm.The H_VPP voltage measured on my evm board is zero.Indicates that there is no work. 

Please tell me the function of rvs pin?

2）The i2c initialization failed because the power of the I2C1_SCL and I2C1_SDA pins has not been low at this time. Will it affect the Linux MLO startup?

If so, then why is the MLO of RTOS not affected?

3）Does linux start the debugging method of mirror MLO assembly stage? I want to track whether the MLO is successfully loaded and running.

This has been bothering me for 8 days and it prevents me from continuing to develop on the Linux system. Please TI experts clearly answer my above questions and provide a correct solution,.

thank you!

Has the EVM always exhibited these issues, or just recently?

How is the custom 913 YUV camera connected to the system?  Is it via the ZIF connector J5? 

During the testing listed above, was the camera connect or disconnected?  If connected - consider trying with camera removed from system.

What power supply is being used with the system?  Insufficient power supplies will cause strange behavior.

When measuring the voltage on the I2C signals - was that after an image attempted to boot?  Are the signals high if no image is booted (and no camera attached)?

Hi,

The evm started to be normal. After I ported the driver of the 913 yuv camera to the linux system and started running app.out,

this problem has been ported.

The custom 913 YUV camera is connected to the system through the Vision Application Board PCB Drawing Rev D and 914

deserialization board link

After the MLO mirroring of Linux that cannot be loaded from the SD card, I removed the link of the camera.

The above tests were performed without linking the yuv camera.

The power supply uses a 12v regulated source. If it is due to a power supply problem, the problem is that the rtos

image can be read from the SD card normally?So the power supply problem can be ruled out.

Can you answer the question I raised above?

I want to modify the value of gpio in the start.S of spl to determine whether rbl has loaded the mlo into the internal

sram and run it, but it failed. What are your good ways to debug in the start.s phase?

At the above points of the system, whether it is started or not, the voltage of i2c1 measured is high.

Hi, ti expert

The evm started to be normal. After I ported the driver of the 913 yuv camera to the linux system and started running app.out,

this problem has been ported.

The custom 913 YUV camera is connected to the system through the Vision Application Board PCB Drawing Rev D and 914

deserialization board link

After the MLO mirroring of Linux that cannot be loaded from the SD card, I removed the link of the camera.

The above tests were performed without linking the yuv camera.

The power supply uses a 12v regulated source. If it is due to a power supply problem, the problem is that the rtos

image can be read from the SD card normally?So the power supply problem can be ruled out.

Can you answer the question I raised above?

I want to modify the value of gpio in the start.S of spl to determine whether rbl has loaded the mlo into the internal

sram and run it, but it failed. What are your good ways to debug in the start.s phase?

At the above points of the system, whether it is started or not, the voltage of i2c1 measured is high.

Hi, ti expert

Because of this problem, my development board cannot work normally, and I cannot continue other things.

Every time I raised my question, I didn't receive a direct reply. Instead, it was the question you asked me.

After replying to your question, I waited for several days. So far I have not received any method to solve this problem or how to locate it.

If you are helping me analyze this problem, please let me know that you are trying to find a solution. If you cannot solve this problem,

please tell me clearly, thank you!

I believe several different people are monitoring this thread - with different areas of expertise.  I am the hardware support.  The reason I asked about power supply is because Linux requires more power than RTOS.  I wanted to ensure the power supply has enough current to supply the EVM.  We recommend a 60W power supply (12V at 5A).  

From my understanding - the EVM (hardware and software) was functioning fine until you connected custom camera and updated Linux binary.  Yes?  Since then you have removed the camera, and the issue still exists.  Can you still use RTOS and/or older Linux binary and boot the EVM without issue?  I'm just trying to rule out any possible issue(s) with hardware and power. 

Hi,

First of all, let me make sure that the power supply is the same as before. I also use 12V at 5A as you said.

In fact, the description of these problems has been very detailed before, and I have to repeat it here.

Using RTOS mirroring can load MLO from SD card and load appimage program, but after starting mlo,

the error message "SBL initial configuration failed" is prompted.I have confirmed that the voltage of the i2c1 bus after evm is always low.

Please don’t ask me the same question, I think it’s useless to me,It's just a waste of everyone's time.

I want to know, if there is a problem with the I2c1 bus and the information in the eeprom cannot be read and written normally,

will the system fail to start normally? For example, ddr cannot be initialized normally and so on. Can you tell me the information stored in eeprom?

I want to write this information directly to uboot's mlo instead of reading it from eeprom.

Can senior software engineers take a look at my problem?

The EEPROM contents are defined in the EVM User's Guide, Section 3.6.25 Configuration EEPROM

EEPROM Usage in u-boot can be seen in this file
git.ti.com/gitweb

Hi, 

Now the i2c1 bus of my evm board cannot normally read the eeprom configuration to initialize the external ddr, so I want to know the configuration parameters obtained from eeprom when the tda2ex17 evm board starts normally.

Can you tell me?

Hi, Robert

According to what you said, I have found Section 3.6.25 Configuration EEPROM, but I want to know the eeprom,

Various possible values are listed here，But I want a certain value of the tda2ex17 evm board, please tell me?

please answer my questions clearly:

I want to know, if there is a problem with the I2c1 bus and the information in the eeprom cannot be read and written normally,

will the system fail to start normally? For example, ddr cannot be initialized normally and so on.Can you tell me the information stored in eeprom?

Hi vishal,

I think Robert doesn't understand my question, and every time I answer it puzzles me. This wastes everyone's time.

Can Vishal help me answer my questions?

How can I not correctly read the eeprom data through i2c1 after MLO is started?

Will it affect the initial external ddr? Because the i2c1 bus voltage is always low and cannot work normally,

how can I skip reading the contents of eeprom to initialize the external memory?

Hi Yanmm,

In the other thread I have explained how data from EEPROM is used in u-boot to configure memory.
https://e2e.ti.com/support/processors/f/791/p/940606/3497155#3497155

If I2C1 has issues on the board, there are more issues to follow.

EEPROM ion I2C1 is used to identify board information and configure u-boot accordingly.
Note that PMIC is also on I2C1 and none of the PMIC operations will work as well.

The I2C hardware issue needs to be resolved first, instead of trying to work around it.

Regards,
Vishal

Hi vishal

Thank you very much for your reply, it gave me hope.

You are right, but I can start and witness the appimage running normally when I use mlo of rtos,

but it prompts that i2c1 fails to read and write, so I think i2c1 has little effect on pmic, just use the default value.

I am running mlo now At the beginning of the memory, there is no information.

So I want to solve the memory initialization problem first, instead of reading the configuration information from the eeprom,

write this information directly into the program and see if there is any change

Hi,expert,

This thread did not solve my problem, how can it show that it has been resolved, I am very disappointed, TI experts are also so irresponsible.

The questions raised are not answered positively, and the reposted posts are not able to solve the problem. Then who should we ask for help when we encounter problems.

Hi,

Thread is not resolved. It is still in open state.

We showed you the u-boot section where EEPROM data is used to initialize the board. If the board has issue with accessing EEPROM the initialization would not be correct.

Regards,
Vishal

Hi vishal,

I am glad to receive your reply.Let me know you are still paying attention to this issue.

The link you provided just pointed out that uboot reads the eeprom file, but my idea is to write the eeprom content directly

in the program in the ti_i2c_eeprom_dra7_get function.

Please share the configuration content of eeprom of tda2ex7-evm, thank you!

The EEPROM contents were mentioned by Robert in previous response

- EVM User's Guide, Section 3.6.25 Configuration EEPROM
- I think the only change from what is documented in User Guide will be the revision.  This will likely be a 0x3.

Hi, vishal

According to your answer, I checked "EVM User's Guide, Section 3.6.25 Configuration EEPROM" again.

The screenshot of eerpom is as follows

The 0x3 you gave refers to the field in the red box in the above figure, but I want to know the field content of the green box, which is on the tad2ex17-evm board.

The ID.BOARD_NAME field is different, the program execution process is different.This is why I still need you to share the content of eeprom.

Or can you tell me, when i2c1 is not working, you want em to boot the kernel to the system normally, what needs to be modified?

Thank you

Hi Yanmm,

The value 0x3 that Robert mentioned is for the Red Box.

In the u-boot file I mentioned, look for configurations that are selected based on board_is_dra71x_evm() API and make them the default configuration.

Regards,
Vishal

Hi, Vishal

Okay, then proceed to answer the unanswered questions as follows:

The ID.BOARD_NAME field is different, the program execution process is different.This is why I still need you to share the content of eeprom.

Or can you tell me, when i2c1 is not working, you want em to boot the kernel to the system normally, what needs to be modified?

Vishal and I have provided the answer.  Again - as specified in the User Guide, the ID.BOARD_NAME field is '‘DRA79x,DRA71x'

Robert Eschler are sure that the user manual is correct? if it is correct, I won't have any questions.

You should read the eeprom value from the actual evm board, not just view it from the manual.

Please answer me clearly ： when i2c1 is not working, you want em to boot the kernel to the system normally, what needs to be modified?

Hi Yanmm,

The EEPROM is correct, the software also looks for same value. Please refer to board_is_dra71x_evm() API in u-boot code.
https://git.ti.com/gitweb?p=glsdk/psdkla-u-boot.git;a=blob;f=board/ti/dra7xx/evm.c;h=ff438d75bd148c9db1db657009ccd83df753a51c#l41

"When i2c1 is not working" - This question is not valid. The peripherals on the board are expected to work and the software expects the i2c1 to work. If those peripherals don't work, it would be unexpected behavior.

I already suggested or provided direction on what you should look for and change in the u-boot to not rely on EEPROM for board configuration. We don't have a reference software to show that.

Regards,
Vishal

Additional detail, the API only tries to match eight characters from board name and not the entire name.

#define board_is_dra71x_evm()           board_ti_is("DRA79x,D")

HI, vishal

Great vishal, the above is exactly the value I need.

But my evm board i2c1 can't work normally, which leads to the failure to boot zImage.

Now I also write the eeprom configuration information into the program, and the serial port does not have any

information when the spl loads uboot.img. I don’t know where else I need to modify it. Can you help me? Check it?