XAPP1079 in vivado 2018.3

vicfer89 over 6 years ago

I'm trying to use XAPP1079 to Vivado 2018.3.

It works properly when the compiled code is lanched in debug, but if it is loaded into flash memory it does not work.

Have somebody faced this issue?

Thanks in advance.

Parents

jafoste4 over 6 years ago

What hardware are you using?
-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vicfer89 over 6 years ago in reply to jafoste4

Hi Joshua,

I've tried flashing both Zedboard and Enclustra Mars ZX3.

Thanks un advance,
Kindest regards.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

vicfer89 over 6 years ago in reply to jafoste4

Hi Joshua,

I've tried flashing both Zedboard and Enclustra Mars ZX3.

Thanks un advance,
Kindest regards.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

jafoste4 over 6 years ago in reply to vicfer89

Hi,
Does it work when booting from SD Card?

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vicfer89 over 6 years ago in reply to jafoste4

Hi Josh,

Same bahavior as for QSPI...

Thanks for the support

-Víctor
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 6 years ago in reply to vicfer89

Hi Victor, Can you share your .bif file when generating the Sd card image? Also just to confirm, are you changing the boot mode jumpers when trying to boot from QSPI or SD?

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

vicfer89 over 6 years ago in reply to jafoste4

Hi Josh,

.bif is as follows:

//arch = zynq; split = false; format = BIN
the_ROM_image:
{
[bootloader]C:\Test_Vivado\project_2_CPP\project_2_CPP.sdk\main_fsbl\Debug\main_fsbl.elf
C:\Test_Vivado\project_2_CPP\project_2_CPP.sdk\design_1_wrapper_hw_platform_0\design_1_wrapper.bit
C:\Test_Vivado\project_2_CPP\project_2_CPP.sdk\main_ARM0\Debug\main_ARM0.elf
C:\Test_Vivado\project_2_CPP\project_2_CPP.sdk\main_CPU1\Debug\main_CPU1.elf
}

Thanks in advance.

Regards,

jafoste4 over 6 years ago in reply to vicfer89

Hi Vic,

It looks like your generating everything correctly.
Following the order of FSBL - Bitstream - Application.
Are you sure your jumper position is correct?

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vicfer89 over 6 years ago in reply to jafoste4

Hi Josh,

I'm researching in that guideline... I think that the issue is caussed by BSP or FSBL generation. Is it possible that Vivado/SDK 2018 does not incorporate AMP capability as well?

Thanks for all your support.
Regards.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 6 years ago in reply to vicfer89

Did you specify to include the AMP in the BSP? Typically when generating a FSBL, you let SDK create its own BSP, you would then need to go back in and modify it for the AMP capabilities if i am remembering correctly.

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vicfer89 over 6 years ago in reply to jafoste4

Hi Jeff,

I did it. At BSP for ARM-01 I set the flag -DUSE_AMP = 1. But i didn't perform any change at FSBL, and as you said, i let SDK creating its own BSP for FSBL. Do you have some guidelines about what have to be changed at both BSP and FSBL? and, of course... would you be so kind as to share them with me?

Thanks in advance and for all your support.

Victor.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 6 years ago in reply to vicfer89

Hey Victor,

Please share your boot.bin file with me and I'll try it on my board.

Thanks,
Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vicfer89 over 6 years ago in reply to jafoste4

Hi Josh,

Please, find at the following link the whole SDK project: https://www.dropbox.com/s/5kjvx5g7jcc64wo/project_2_CPP.sdk.7z?dl=0

.BIN can be found under main_fsbl > bootimage.

Hope it can clarify what happens...

Thanks in advance.
Kindest regards,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel