On 19/06/2021 16:35, dufa...@hda.com wrote:
I'm getting back to this as I have the HyperRAM working so I'm trying to set up
appropriate linker settings.
On Jun 10, 2021, at 01:43 , Sebastian Huber
wrote:
The initial stack needs to be in an accessible memory area. Currently it is
placed
I'm getting back to this as I have the HyperRAM working so I'm trying to set up
appropriate linker settings.
> On Jun 10, 2021, at 01:43 , Sebastian Huber
> wrote:
>
> The initial stack needs to be in an accessible memory area. Currently it is
> placed in this linker output section:
>
>
On 09/06/2021 20:47, Peter Dufault wrote:
Similar comments apply to RAM. I'll be adding HyperRAM attached to FlexSPI port A chip select 2
and it won't be setup until we get past "bsp_start_hook_0()". So initial stack needs to
be in on-chip RAM and we can't access anything outside of on-chip R
On 9/6/21 5:05 pm, Christian Mauderer wrote:
> On 09/06/2021 01:52, Chris Johns wrote:
>> On 8/6/21 8:26 pm, Sebastian Huber wrote:
>>> On 08/06/2021 05:07, Chris Johns wrote:
On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't
need
documentation changes because
Let's get back to the patch itself and the initialization of "FlexSPI"
peripheral.
The FlexSPI is one of the "imxrt" on-chip devices that can have flash attached
to it, and that the on-chip boot ROM knows how to probe, configure, and then
boot from. The "imxrt" chips don't have on-chip flash,
On 09/06/2021 01:52, Chris Johns wrote:
On 8/6/21 8:26 pm, Sebastian Huber wrote:
On 08/06/2021 05:07, Chris Johns wrote:
On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
documentation changes because the options in the
waf based build system are now documented dire
On 8/6/21 8:26 pm, Sebastian Huber wrote:
> On 08/06/2021 05:07, Chris Johns wrote:
>> On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
>> documentation changes because the options in the
>>> waf based build system are now documented directly in the yaml files and
>>> p
On Tue, Jun 8, 2021 at 5:37 AM Christian Mauderer wrote:
>
> Hello Chris,
>
> On 08/06/2021 12:05, Chris Johns wrote:
> > On 8/6/21 7:08 pm, Christian Mauderer wrote:
> >> Hello Chris,
> >>
> >> On 08/06/2021 05:07, Chris Johns wrote:
> >>> On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the
Hello Chris,
On 08/06/2021 12:05, Chris Johns wrote:
On 8/6/21 7:08 pm, Christian Mauderer wrote:
Hello Chris,
On 08/06/2021 05:07, Chris Johns wrote:
On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
documentation changes because the options in the
waf based build
On 08/06/2021 05:07, Chris Johns wrote:
On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
documentation changes because the options in the
waf based build system are now documented directly in the yaml files and printed
if you generate the default config.
Hmm I am not
On 8/6/21 7:08 pm, Christian Mauderer wrote:
> Hello Chris,
>
> On 08/06/2021 05:07, Chris Johns wrote:
>> On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
>> documentation changes because the options in the
>>> waf based build system are now documented directly in the
Hello Chris,
On 08/06/2021 05:07, Chris Johns wrote:
On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
documentation changes because the options in the
waf based build system are now documented directly in the yaml files and printed
if you generate the default config.
On 7/6/21 6:40 pm, Christian Mauderer wrote:> I think the Options don't need
documentation changes because the options in the
> waf based build system are now documented directly in the yaml files and
> printed
> if you generate the default config.
Hmm I am not sure I agree with the premise the Y
Hello Gedare,
I think the Options don't need documentation changes because the options
in the waf based build system are now documented directly in the yaml
files and printed if you generate the default config. But I think I
should add a documentation for the ARM PLL. I'll send a patch as soon
does this one need doco update for the option changes?
On Fri, Jun 4, 2021 at 1:48 AM Christian Mauderer
wrote:
>
> Calling the memory FLASH and EXTRAM instead of FLEXSPI and SDRAM makes
> it simpler to support other types of external RAM. This patch also
> removes some of the calculations and im
Calling the memory FLASH and EXTRAM instead of FLEXSPI and SDRAM makes
it simpler to support other types of external RAM. This patch also
removes some of the calculations and improves names and documentation to
avoid pitfalls. It removes a unnecessary memory definition.
Update #4180
---
bsps/arm/
16 matches
Mail list logo
