Beware of that 1PPS signal. A few years ago I bought several GPS modules and
compared the signals. Some differ by exactly 100ns (within 2ns, the accuracy of
my scope) from others, and that is not the width of the pulse, that is much
wider, I compared only the edge that are comes close to the ot
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__ attribu
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
Thanks Arie,
Yes, very true, it depends on your application!
My statement about what makes a good clock is very subjective. This
all depends on your application, your measurement and of course your jitter.
- For Wireless AV, a 10ms gps clock is fine.
- For Wireless Earbuds, a 10us clock is requi
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
Have you ensured that all the code (and support code, systic etc) is in RAM?
Also, Is this an ECCed FLASH? Is the write size correct? We must line cache
the writes on some parts in the PX4 bootloader.
https://github.com/PX4/PX4-Autopilot/blob/main/platforms/nuttx/src/bootloader/common/lib/flash_c
