Update README files.
This commit is contained in:
parent
c6026d7500
commit
5655a9d362
@ -20,8 +20,10 @@ Status
|
|||||||
to support development of the architecture support. This is VERY much
|
to support development of the architecture support. This is VERY much
|
||||||
a work in progress and you should not use this configuration unless you
|
a work in progress and you should not use this configuration unless you
|
||||||
are interested in assisting with the bring-up.
|
are interested in assisting with the bring-up.
|
||||||
|
|
||||||
2019-08-17: The port is code complete. It compiles with no errors or
|
2019-08-17: The port is code complete. It compiles with no errors or
|
||||||
warnings but is untested. Still waiting for hardware.
|
warnings but is untested. Still waiting for hardware.
|
||||||
|
|
||||||
2019-08-20: I have the board and started the debug. However, the
|
2019-08-20: I have the board and started the debug. However, the
|
||||||
very first image that I wrote to FLASH seems to have "bricked" the
|
very first image that I wrote to FLASH seems to have "bricked" the
|
||||||
board. I believe that the S32K118 resets into a bad state and
|
board. I believe that the S32K118 resets into a bad state and
|
||||||
@ -29,6 +31,10 @@ Status
|
|||||||
the world. I will continuing the bring-up using the S32K146EVB
|
the world. I will continuing the bring-up using the S32K146EVB
|
||||||
where I can run from SRAM for the initial bring-up.
|
where I can run from SRAM for the initial bring-up.
|
||||||
|
|
||||||
|
These bring-up issues were addressed with S32K146EVB. It is not probably
|
||||||
|
safe to try the S32K118EVB again (if I can figure out how to break into
|
||||||
|
my bricked system).
|
||||||
|
|
||||||
Serial Console
|
Serial Console
|
||||||
==============
|
==============
|
||||||
|
|
||||||
|
@ -21,9 +21,13 @@ Status
|
|||||||
not yet been tested. This is VERY much a work in progress and you
|
not yet been tested. This is VERY much a work in progress and you
|
||||||
should not use this configuration unless you are interested in
|
should not use this configuration unless you are interested in
|
||||||
assisting with the bring-up.
|
assisting with the bring-up.
|
||||||
|
|
||||||
2019-08-20: Initial testing, I am running out of SRAM to avoid the
|
2019-08-20: Initial testing, I am running out of SRAM to avoid the
|
||||||
brickage problems I had with the S32K118EVB (i.e., with
|
brickage problems I had with the S32K118EVB (i.e., with
|
||||||
CONFIG_BOOT_RUNFROMISRAM=y)
|
CONFIG_BOOT_RUNFROMISRAM=y).
|
||||||
|
|
||||||
|
The NSH configuration now appears work correctly. Only verified when
|
||||||
|
running SRAM at present.
|
||||||
|
|
||||||
Serial Console
|
Serial Console
|
||||||
==============
|
==============
|
||||||
|
Loading…
x
Reference in New Issue
Block a user