ARM JUNO BOARD R2

Hello,

There's a lot of information on connected Community (CC) that might help you. Look at the Instructions for Using the Linaro deliverables and FAQs on these pages. Also refer to this Getting Started Guide (referenced from the CC pages). http://infocenter.arm.com/help/topic/com.arm.doc.den0928f/DEN0928F_juno_arm_development_platform_gsg.pdf

Some brief responses, these are very "open" questions...

>How to generate the image for Juno board

There are GCC cross compilers referenced from the standard instructions. There's also an FAQ on developing baremetal code (running post Trusted Firmware). The supplied OE LAMP stack for Juno also includes a cross compiler so you can natively build Linux apps.

>what are the images we will get after compilation, how to load the images into target board .

It depends how and what you are building (see above). Baremetal code development is going to typically rely on a JTAG debugger to allow you to load code directly into RAM and then debug it. If you are working on top of Linux, you have many more options  (e.g. can simply mount a remote drive or use something like SCP to copy things across and debug remotely via GDBserver).

>Description about each image and what are all the peripherals is initialized by each image

See the Getting Started Guide above & also the external Trusted Firmware (TF) documentation.

>Description about each image and what are all the peripherals is initialized by each image

It depends: Some basic peripherals (DDR for example) are configured in the early boot stages of TF. Some peripherals (Ethernet) are configured by drivers later in the SW stack.

> when board is powered on, how will be the boot flow. where user has control to load the application image

By default a single lead CPU will boot - other CPUs will be woken by Linux.

HTH

MarkN.

Hello,

There's a lot of information on connected Community (CC) that might help you. Look at the Instructions for Using the Linaro deliverables and FAQs on these pages. Also refer to this Getting Started Guide (referenced from the CC pages). http://infocenter.arm.com/help/topic/com.arm.doc.den0928f/DEN0928F_juno_arm_development_platform_gsg.pdf

Some brief responses, these are very "open" questions...

>How to generate the image for Juno board

There are GCC cross compilers referenced from the standard instructions. There's also an FAQ on developing baremetal code (running post Trusted Firmware). The supplied OE LAMP stack for Juno also includes a cross compiler so you can natively build Linux apps.

>what are the images we will get after compilation, how to load the images into target board .

It depends how and what you are building (see above). Baremetal code development is going to typically rely on a JTAG debugger to allow you to load code directly into RAM and then debug it. If you are working on top of Linux, you have many more options  (e.g. can simply mount a remote drive or use something like SCP to copy things across and debug remotely via GDBserver).

>Description about each image and what are all the peripherals is initialized by each image

See the Getting Started Guide above & also the external Trusted Firmware (TF) documentation.

>Description about each image and what are all the peripherals is initialized by each image

It depends: Some basic peripherals (DDR for example) are configured in the early boot stages of TF. Some peripherals (Ethernet) are configured by drivers later in the SW stack.

> when board is powered on, how will be the boot flow. where user has control to load the application image

By default a single lead CPU will boot - other CPUs will be woken by Linux.

HTH

MarkN.