On 6/26/19 12:25 PM, Rouven Czerwinski wrote:
>> And what is the reason behind decreasing 16 from returning address:
>>
>> MX8MQ_ATF_BL33_BASE_ADDR - 16
>>
>> I removed "16" for im8mq in Barebox and still works.
>
> This puts some distance between the stack and your execution address.
> As long a
On Wed, Jun 26, 2019 at 09:31:14AM +0200, Sascha Hauer wrote:
> On Wed, Jun 26, 2019 at 06:58:42AM +0200, Rouven Czerwinski wrote:
> > The HAB interface for i.MX8MQ only implements the retrieval of status
> > and events. The SoC status is retrieved using the TF-A SIP API found in
> > the downstream
> And what is the reason behind decreasing 16 from returning address:
>
> MX8MQ_ATF_BL33_BASE_ADDR - 16
>
> I removed "16" for im8mq in Barebox and still works.
This puts some distance between the stack and your execution address.
As long as nobody is writing to the stack pointer before increasi
Thanks Rouven.
And what is the reason behind decreasing 16 from returning address:
MX8MQ_ATF_BL33_BASE_ADDR - 16
I removed "16" for im8mq in Barebox and still works.
The PLAT_NS_IMAGE_OFFSET is identical for imx8mq and imx8mm. Do you have any
idea why the firmware is not returned to this addre
>>>
>>> AFAIR this only happened for linker variables that point to absolute
>>> addresses. Differences between addresses also worked with the older
>>> compilers, and I think this is what your patch does:
>>
>> No. my patch just for new toolchain. with old toolchain it has no effect,
>> Because al
On Wed, 2019-06-26 at 08:46 +, Yazdani, Reyhaneh wrote:
> Hello everyone,
>
>
> On the process of bring-up imx8mm board, I am at the point that load
> bl31 and
> jump to ATF.Upon exit from ATF's initialization routine, the
> execution level
> should be EL2.
>
> My question is about imx8mq_at
Hello everyone,
On the process of bring-up imx8mm board, I am at the point that load bl31 and
jump to ATF.Upon exit from ATF's initialization routine, the execution level
should be EL2.
My question is about imx8mq_atf_load_bl31 function.
After copy BL31 into OCRAM address, the function sets up t
This commit removes the fix for the upstream devicetree where eMMC was remapped
to the sdhci interface. This is no longer needed since sdhost driver is now
functional in barebox. A similar change was done to the R.Pi 3 devicetree in
9036d1db.
In fact, this remap prevented CM3 from booting if bareb
On Wed, Jun 26, 2019 at 06:58:51AM +0200, Rouven Czerwinski wrote:
> Add piggydata verification before the ARM uncompress function.
> This calculates the sha256sum of the compressed barebox binary and only
> continues if the builtin sha256sum matches the calculated sha256sum.
>
> Signed-off-by: Ro
On Wed, Jun 26, 2019 at 06:58:48AM +0200, Rouven Czerwinski wrote:
> quiet_cmd_kwb_image = KWB $@
>cmd_kwb_image = scripts/kwbimage -p $< $(OPTS_$(@F)) -o $@
> diff --git a/scripts/imx/imx-image.c b/scripts/imx/imx-image.c
> index a7f1421..7169bf7 100644
> --- a/scripts/imx/imx-image.c
On Wed, Jun 26, 2019 at 06:58:42AM +0200, Rouven Czerwinski wrote:
> The HAB interface for i.MX8MQ only implements the retrieval of status
> and events. The SoC status is retrieved using the TF-A SIP API found in
> the downstream imx TF-A. After calling into the TF-A the passed data
> structures ne
On Tue, Jun 18, 2019 at 06:17:52PM +0800, 张忠山 wrote:
> > No, it is corrected during runtime in relocate_to_current_adr(). It
> > seems older compilers need a runtime relocation fixup for this.
>
> Yes, in relocate_to_current_adr() the address all be fixed up.
>
> But if _barebox_image_size, __bss
Hi Antony,
On Wed, Jun 19, 2019 at 01:49:16PM +0300, Antony Pavlov wrote:
> Tap network interface initialization in sandbox
> barebox leads to segfault under Debian Buster/Sid.
>
> The problem is that strcpy(dev, ifr.ifr_name) inside
> tap_alloc() tries to alter read-only data passed
> by tap_pro
On Tue, Jun 25, 2019 at 09:31:45AM +0200, Rouven Czerwinski wrote:
> This fixes a compiler warning because len is size_t and
> RNG_FAIL_EVENT_SIZE was cast to uint32_t.
>
> Signed-off-by: Rouven Czerwinski
> ---
> drivers/hab/habv4.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Appli
On Fri, Jun 21, 2019 at 11:20:48AM +0200, Rouven Czerwinski wrote:
> Makefile.imx uses the .simximg und .usimximg extensions for signing of
> the images. Remove the unused .imximx.signed and also add the .csfbin
> files generated by the NXP CST tool.
>
> Signed-off-by: Rouven Czerwinski
> ---
>
15 matches
Mail list logo
