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
Related to this, I have a GPS receiver generating PPS interrupts on SAME70.
It would be a perfect GMC - Atomic clock sync!
I will look at this when I get a chance. I have a lot of upstream
contributions from HW platforms I have done
over the last 5 years or so with myself and others ... I need some
Yes, it’s good stuff. I will look at it next year.
> On Dec 7, 2022, at 5:41 PM, Nathan Hartman wrote:
>
> On Tue, Dec 6, 2022 at 11:16 PM James Dougherty wrote:
>
>> Great project! I've done a few commercial implementation of PHY
>> timestamping protocols - IEEE1588 for Ethernet 802.3
>> and
On Tue, Dec 6, 2022 at 11:16 PM James Dougherty wrote:
> Great project! I've done a few commercial implementation of PHY
> timestamping protocols - IEEE1588 for Ethernet 802.3
> and the WLAN version (802.11v2012) for 802.11n. Products with that
> technology are still shipping today (but that was
