Hi Greg,
Thank you for your suggestions; I did add the -mlong-calls to the platform
Make.defs
-ARCHCFLAGS = -fno-builtin
+ARCHCFLAGS = -fno-builtin -mlong-calls
I tried it out, same issue. Let me know if you have other ideas; I wonder
if anyone has done
in-system programming like this before wit
Hi Greg,
No,l I don't, the relevant extract from make V=1 is as below!
arm-none-eabi-gcc" -- -fno-builtin -Wall -Wstrict-prototypes -Wshadow
-Wundef -fno-strict-aliasing -g -Os -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16
-mfloat-abi=hard -I.
I will test that out tomorrow...
Thank you!
-James
On Mo
Do you have the compiler option -mlong-calls selected? That is necessary
in order to call from the FLASH address space (at 0xxx ) to the SRAM
address space (2xxx ).
he whole internal flash because of the above.
>> >
>> > Best regards,
>> > Petro
>> >
>> > пт, 9 груд. 2022 р. о 07:56 David Sidrane
>> пише:
>> >
>> >> Have you ensured that all the code (and support code, systic etc) is in
&
gt;
> >>
> >>
> https://github.com/PX4/PX4-Autopilot/blob/main/platforms/nuttx/src/bootloader/common/lib/flash_cache.c
> >>
> >>
> >> David
> >> -Original Message-
> >> From: James Dougherty
> >> Sent: Friday, Decemb
https://github.com/PX4/PX4-Autopilot/blob/main/platforms/nuttx/src/bootloader/common/lib/flash_cache.c
>
>
> David
> -Original Message-
> From: James Dougherty
> Sent: Friday, December 9, 2022 12:46 AM
> To: dev@nuttx.apache.org
> Subject: Re: SAM-E70 progmem - in sy
tloader/common/lib/flash_cache.c
>>
>>
>> David
>> -----Original Message-----
>> From: James Dougherty
>> Sent: Friday, December 9, 2022 12:46 AM
>> To: dev@nuttx.apache.org
>> Subject: Re: SAM-E70 progmem - in system programming and RAMFUNCS
>
2 12:46 AM
> To: dev@nuttx.apache.org
> Subject: Re: SAM-E70 progmem - in system programming and RAMFUNCS
>
> Thank you Greg, Thank you David!
>
> I did check that is correct:
>
> arch/arm/src/samv7/sam_start.c - 344:356
>
> /* Copy any necessary code sections from FLA
/flash_cache.c
David
-Original Message-
From: James Dougherty
Sent: Friday, December 9, 2022 12:46 AM
To: dev@nuttx.apache.org
Subject: Re: SAM-E70 progmem - in system programming and RAMFUNCS
Thank you Greg, Thank you David!
I did check that is correct:
arch/arm/src/samv7/sam_start.c - 344
Thank you Greg, Thank you David!
I did check that is correct:
arch/arm/src/samv7/sam_start.c - 344:356
/* Copy any necessary code sections from FLASH to RAM. The correct
* destination in SRAM is geive by _sramfuncs and _eramfuncs. The
* temporary location is in flash after the data ini
On 12/8/2022 5:55 AM, David Sidrane wrote:
Is the NVIC_VTABLE repointed to the RAM vectors?
The RAM functions are like .bss: There is a storage area of code that
that is copied into RAM only power up. But the symbols associated with
the RAMFUNCs are defined by the linker script to be the ad
Is the NVIC_VTABLE repointed to the RAM vectors?
-Original Message-
From: James Dougherty
Sent: Thursday, December 8, 2022 12:40 AM
To: dev@nuttx.apache.org
Subject: Re: SAM-E70 progmem - in system programming and RAMFUNCS
RAMFUNCS certainly works for this funcs with __ramfuncs__
RAMFUNCS certainly works for this funcs with __ramfuncs__ attributed tagged
funcs for the eefr procs. And I do see ramvectors load from OpenOCD..
(gdb) lo
Loading section .text, size 0x30e14 lma 0x40
Loading section .ARM.exidx, size 0x8 lma 0x430e14
Loading section .data, size 0x1158 lma 0x430
I did a quick review of this tonight at least with RAMFUNCS and COPYTORAM
defines.
I read through most of the code related to copying the vectors to ram. I
didn't find where
exception_common gets put into the ram-vectors for the CM7... maybe someone
knows?
Seems like something is missing...
jfd@ar
Hi Petro,
Thank you for your email (the silence was deafening) :)
The SAME70-XPlained board in master would be very similar and a good test
case.
In doing some archaeology on master, I found that the XULT board has
RAMFUNCS enabled!
I'm using SAME70N21B, configuration parameters as below:
#
# AR
Hello James,
I've been working with SAMe70 based device and can try to take a look at a
case that you are talking about.
Do you have any specific config that I can start from?
In general I expect that if you fully relocate your program to SRAM you
should be capable of reprogramming a full flash,
16 matches
Mail list logo
