How to deal with the ARM error while debugging adrv9009 no-os code?

1000floors on Nov 22, 2021

Hi,I am using the hdl 'master' branch . And i am using no-os master branch. And I am using the project design for zc706 and EVAL-ADRV9008/9.

I am migrating the reference design to a custom design board . While I am debug the no-os program step over this line:

https://github.com/analogdevicesinc/no-OS/blob/f1620319b5c77412f44ded55abc5b8aa7df9697e/drivers/rf-transceiver/talise/api/talise_cals.c#L83

the console shows a error message showed in the below picture.

I don't know what reason cause this error , is it imply that the arm of zynq has some problem?

Can anyone tell what might cause the error.

Thanks.

uint32_t TALISE_verifySpiReadWrite (taliseDevice_t *device)
{
	talRecoveryActions_t retVal = TALACT_NO_ACTION;
	adiHalErr_t halError = ADIHAL_OK;
	uint8_t spiReg = 0;

#if TALISE_VERBOSE
	halError = talWriteToLog(device->devHalInfo, ADIHAL_LOG_MSG, TAL_ERR_OK,
				 "TALISE_verifySpiReadWrite()\n");
	retVal = talApiErrHandler(device, TAL_ERRHDL_HAL_LOG, halError, retVal,
				  TALACT_WARN_RESET_LOG);
#endif

Top Replies

srimoyi
Dec 10, 2021 in reply to 1000floors +1 verified
Yes.. That could be the issue. The profile that you are using should have ORX disabled.

.obsRxChannelsEnable = TAL_ORXOFF

That is why, it is always recommended to generate the profile with your required…
1000floors Dec 11, 2021 in reply to srimoyi +1

Hi,@srimoy Thanks .The problem solved.I disable the orx path here: talise_config.c#L205 with .obsRxChannelsEnable = TAL_ORXOFF , and I input no signal to the receiver port ,the RX TIA filter calibration…

0 andreid1994

on Nov 24, 2021 9:40 AM
Hello,

This seems similar to this question. Let me know if it helps.

Regards,
Andrei
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 1000floors on Nov 25, 2021 3:07 AM in reply to andreid1994

Hi,andreid1994 .Thanks for your help.

I have read your suggest answer. I noted that the answer suggest to reduce the SPI speed to 10 MHz .

I make it done by change the number here.

According to the answer suggest , I attach it in the picture below, I should communicate with the scratch pad and check whether the read writes are fine.

I found that the function "TALISE_initialize" call the function "TALISE_setSpiSettings" which link : here .The function "TALISE_setSpiSettings" call the function "TALISE_verifySpiReadWrite" ,which can check the scratch pad register 0x00A .And while call the function ""TALISE_initialize" ，write and read 0xB6 and 0x49 to scratch pad register works fine.

I call "TALISE_verifySpiReadWrite" after this line in headless.c. If write 0XB6 to the scratch pad register 0x00A , then the spi read will be 0x49. every bit of 0xB6 reversed .I attached the output of console in the below picture. Can you give me some tips about this ? I don't know what kind of problem occur to the spi.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 andreid1994

on Nov 26, 2021 8:11 AM in reply to 1000floors
Hello,

What do you mean by the following?

1000floors said:
write and read 0xB6 and 0x49 to scratch pad register works fine.

Does it mean that the scratch pad check works fine while you run the TALISE_initialize function, but does not work if called from the main file?

I think you might find faster and better answers to this question in the design support forum.

Regards,
Andrei
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 1000floors on Nov 26, 2021 9:05 AM in reply to andreid1994

Hi,andreid1994.Thanks for your reply.

andreid1994 said:
Does it mean that the scratch pad check works fine while you run the TALISE_initialize function, but does not work if called from the main file?

Yes. Sometimes the scratch pad check also works fine if called from the main file.Can you move this question to the forum you talked? Thanks.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 andreid1994

on Nov 26, 2021 11:03 AM in reply to 1000floors
Moved to the design forum.

Regards,
Andrei
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 1000floors on Dec 2, 2021 9:48 AM

while I debug step into this line /adrv9009/src/app/app_talise.c#L279, and step over to this line rf-transceiver/talise/api/talise_cals.c#L83 step into and step over to this line TALISE_readArmCmdStatusByte , the value of "cmdStatByte" is 0x0e, keep step over to this line https://github.com/analogdevicesinc/no-OS/blob/cbd8405892eeadc4383a6d8ddc3644fb9a6f4743/drivers/rf-transceiver/talise/api/talise_arm.c#L1130 the console will give error message:

I don't know why this happen most of times but not every time.

andreid1994 said:

Does this happen on the custom design board, or are you seeing this behavior on the example design?

Answer: I move the example design to the custom board then I seeing this error.

andreid1994 said:

If it's not 100% of the time that we see this error, is it possible to reproduce it every time?

Answer: This behavior is kinda random . We can't reproduce it every time.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 1000floors on Dec 6, 2021 6:46 AM

Can anyone help?whether this look like a software or hardware problem?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 srimoyi

on Dec 7, 2021 4:50 AM in reply to 1000floors
Which chip are you using(ADRV9009 or ADRV9008-2/1)? Are you generating the configuration files(including initdata.c) from the TES GUI and then loading that in your custom board and initializing the chip? Are you grounding the ORX path?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 1000floors on Dec 7, 2021 6:41 AM in reply to srimoyi

Hi,srimoyi . Thanks for your reply.

srimoyi said:
Which chip are you using(ADRV9009 or ADRV9008-2/1)?

I am using adrv9009,but i just want to use the rx channel.So i uncomment this line "#define ADRV9008_1" in the file app_config.h . And i remove the tx ip before "axi_adrv9009_tx_jesd" in the hdl block design.

srimoyi said:
Are you generating the configuration files(including initdata.c) from the TES GUI and then loading that in your custom board and initializing the chip?

I am using the default profile tx_bw100_ir122p88_rx_bw100_or122p88_orx_bw100_or122p88_dc122p88 for zc706 .Which file is initdata.c? talise_config.c? I think it is loading in my custom board and initial the chip(How to confirm? I am using vitis gui build the no-os project,I have add the path of "talise_config.c","talise_config.h","talise_config_ad9528.h" into include directories,and the build doesn't output any errors)

srimoyi said:
Are you grounding the ORX path?

Yes, our board connect the pin ORX1_IN+, ORX1_IN− , ORX2_IN+, ORX2_IN− to GND. And float the pin TX2_OUT–, TX2_OUT+.

Any tips? thanks.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 srimoyi

on Dec 7, 2021 9:15 AM in reply to 1000floors
If you are not using the ORX and the TX path, then you need to disable the ORX path and the TX path using TALISE_setRxTxEnable API. Have you done that?

Also, LOL cals and QEC cals will fail as ORX path remains disabled. You should also omit ORX related cals from the init cal mask.

Load the profile that you have downloaded from the website into the TES GUI, and then you need to generate the configuration files(sorry, it is talise_config .c and not initdata.c) into your custom board. Load the stream binary file generated from the GUI as well into your setup as as the stream changes if any will not get included if you dont load the bin file into your custom setup.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel