|author||Tim Lee <email@example.com>||Fri Jan 13 15:00:50 2023 +0800|
|committer||Tim Lee <firstname.lastname@example.org>||Fri Jan 13 09:09:08 2023 +0000|
meta-nuvoton: npcm8xx-tip-fw: update to 0.5.3.0.4.2 Changelog: TIP_FW_L0_0.5.3_L1_0.4.2 ============== - TIP_FW L0 version 0.5.3 and L1 version 0.4.2 L1 - FreeRTOS: in case of assert: print useful info. - NVIC_BMC_reset: clear NVIC int before reloading BMC. - in BMC reset and spurious interrupt reset: read the int number from the active and not the pending. - NVIC_IntHandlerCommon: bug fix: clear correct number. - Big fix: enable all traps in hardware_app_init. - Add task bmc_task to handle BMC reset reload. - Increase heap_size to 0xA000. - HOSTPER: set to 1 till KCS bug is fixed. - Flash: check if FIU1 and FIU 0\CS1 are disabled by OTP bit. - Flash: bug fix: do not enable FIU1 CS2\3. - Flash: Allow using a 4MB flash for image. - Update FreeRTOS to none-MPU version. - Spurious interrupt handling: in case of spurious interrupt print correct int number + NVIC state, and then clear it. - OTP version: use two bits for each version number. - Copy DBGRST too to INTCR2. - Debug log: bug fix: data corruption in case of a 16MB flash. Replace the code so that Debug log is 64KB (one flash block). its location is - split flash for active recovery: 64KB before recovery image. - two flash mode: last block in active flash. - UUID: add full data read (wafer, X\Y, year, work week). Note: debug chips do not contain this info. TIP FW 0.5.1 L0 0.4.0 L1 ============== - Set RCR regs only in PORST. - Change RCR values for TIP reset. - NVIC: print more data on spurious interrupts. - SPIX - set FIU_FIX to SINGLES. Other FIUs remain in INCREASING mode as before. TIP FW 0.5.1 L0 0.4.0 L1 GOOGLE4 ============== - derived from TIP FW 0.5.1 L0 0.4.0 L1 Tested: buid pass and boot up successful with correct TIP FW latest version. Signed-off-by: Tim Lee <email@example.com> Change-Id: I2b5093470d6caa2e26bb287ec7dda3a8d0c4404c
OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.
See the Yocto documentation for the latest requirements
sudo apt install git python3-distutils gcc g++ make file wget \ gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2
sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \ hostname file diffutils diffstat lz4 wget zstd rpcgen patch
git clone https://github.com/openbmc/openbmc cd openbmc
Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called
setup and takes the name of your hardware target as an argument.
The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:
$ . setup <machine> [build_dir] Target machine must be specified. Use one of: bletchley mori s8036 dl360poc mtjade swift e3c246d4i mtmitchell tatlin-archive-x86 ethanolx nicole tiogapass evb-ast2500 olympus-nuvoton transformers evb-ast2600 on5263m5 vegman-n110 evb-npcm750 p10bmc vegman-rx20 f0b palmetto vegman-sx20 fp5280g2 qcom-dc-scm-v1 witherspoon g220a quanta-q71l witherspoon-tacoma gbs romed8hm3 x11spi greatlakes romulus yosemitev2 gsj s2600wf zaius kudo s6q lannister s7106
Once you know the target (e.g. romulus), source the
setup script as follows:
. setup romulus
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile
make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.
For technical discussions, please see contact info below for Discord and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or Discord.
Dive deeper into OpenBMC by opening the docs repository.
The Technical Steering Committee (TSC) guides the project. Members are: