diff options
author | CHLin <CHLIN56@nuvoton.com> | 2019-03-28 10:40:08 +0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2019-04-03 18:13:50 -0700 |
commit | d388343e3b01f780fa621b3c840c2557fcc6e477 (patch) | |
tree | 51144dbb839e43e741acb6dcdea04ddf5991fdfb /util/stm32mon.c | |
parent | 0cb553724da2e424065c482690a2540018f3c60a (diff) | |
download | chrome-ec-d388343e3b01f780fa621b3c840c2557fcc6e477.tar.gz |
npcx7: introduce npcx7m7wc chip and refine memory layout of npcx7m7wb
This CL includes the following changes:
1. add CHIP_VARIANT_NPCX7M7WC in the npcx7 chip configuration files to
define what (RAM, features...) is supported in npcx7m7wc.
2. add the chip id and chip revision id of npcx7m7wc.
3. re-organize the memory of npcx7m7wb from:
current: 320 KB code RAM + 64 KB data RAM.
to : 256 KB code RAM + 128 KB data RAM.
The reason is that the extra 64 KB RAM is excepted to store the WoV
voice data when it operates under RAM mode. Under the limitation of
current memory layout, the 64 KB voice buffer is declared as const
to force it allocated in the code section, which is strange.
This can be fixed after changing the layout.
BRANCH=none
BUG=none
TEST=pass "make buildall"
TEST=with related CLs, change CHIP_VARIANT to npcx7m7wc in
board/npcx7_evb/build.mk; flash image in the internal testing board of
npcx7m7wc; make sure the EC can boot up; check the chip ID and chip
revision ID are correct by console command "version".
TEST=build npcx7m7wb image and test it on npcx7_evb, no symptom found.
Change-Id: I7533c1f5490e151571696ac615da2d0430827a78
Signed-off-by: CHLin <CHLIN56@nuvoton.com>
Reviewed-on: https://chromium-review.googlesource.com/1543062
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: CH Lin <chlin56@nuvoton.com>
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
Diffstat (limited to 'util/stm32mon.c')
0 files changed, 0 insertions, 0 deletions