- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
Hello,
I am working with the Cyclone 10LP Evaluation Kit Booting options and had success testing the boot copier from EPCQ flash (using EPCQ64).
I am now trying to get the XIP Boot mode working and not having success.
Are there any instructions that are not included in AN 736?
I followed AN 736, table 3: BSP Editor Mappings and Figure 5: Exception Vector set to OCRAM. The other steps taken are the same as in the app note.
Thanks in advance
Enlace copiado
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
Did you set the vectors correctly in the IP?
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
I believe they are setup correctly, I have outlined the steps taken so far
1) Platform Designer
- Reset Vector Memory: EPCQ64.avl_mem
- Reset Vector offset: 0x0008_0000
- Reset Vector: 0x0088_0000
- OCRAM Memory Size: 40,500 bytes
- S1 Data Width: 32
2) Launch Eclipse, BSP Editor
- Settings -> Advanced -> hal -> Linker
- ALL CHECKED (My Exception vector is set to OCRAM)
- Linker Section Names all set to OCRAM, except .text and .entry (EPCQ64_avl_mem)
- Click generate
3) Build Project
- Build project to generate .elf
- Run Make Target -> Build -> mem_init
4) Convert Programming File
- Flash Loader added
- SOF file loaded (compressed checked)
- Hex Data loaded (Absolute addressing) --> starts at 0x0008_0000
***Convert Program File Error : Size of file(s) in EPCQ64 exceeds memory capacity***
After this point it is saying my EPCQ64.hex is bigger than the memory capacity.
I did notice my hex files were empty (EPCQ64 and OCRAM). I cleaned the project and rebuilt the mem_init scripts. but no luck
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
Hi ENGR_24,
Any updates? Could you try the following workaround as it may be applicable to this issue:
https://www.macnica.co.jp/en/business/semiconductor/articles/intel/130281/
Regards,
Fakhrul
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
Do the steps I outlined from above look right?
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
Hi ENGR_24,
Any updates?
Regards,
Fakhrul
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
As we haven't received a response to our previous notification, this thread will be transitioned to community support. We hope all your concerns have been addressed. If you have any new questions, please feel free to open a new thread to receive support from Intel experts. Otherwise, community users will continue to assist you here. Thank you.

- Suscribirse a un feed RSS
- Marcar tema como nuevo
- Marcar tema como leído
- Flotar este Tema para el usuario actual
- Favorito
- Suscribir
- Página de impresión sencilla