dev

dev@openharmony.io

October 2020

2 participants
2 discussions

HiSilicon hi3861 build (wifiiot): PATH gotcha (and other setup)
by Christopher Tom 30 Oct '20

30 Oct '20

Hopefully can save others a little time. The PATH to the gcc executables can't end with a '/' character or you will get an error like "riscv32-unknown-elf-ld: cannot find -lgcc" (see get_lib_path in vendor/hisi/hi3861/hi3861/build/scripts/scons_env_cfg.py). eg. PATH=/gcc_riscv32/bin not PATH=/gcc_riscv32/bin/ Other requirements: the PATH to the executables must contain gcc_riscv32 and end with bin, and libgcc.a must be in the directory ../lib/gcc/riscv32-unknown-elf/<gcc version number>/ relative to the executables directory. (ie. must be a relatively standard directory structure). Might be relevant for those thinking of putting the executables in $HOME/bin. The scons_env_param_check in scons_utils.py performs the same check as get_lib_path and supports ending with '/' so it may be fair to ask HiSilicon to call this function instead. I also needed to install the scons, pycrypto, and ecdsa packages for the HiSilicon hi3861 build (available through pip).

2 1

Problem accessing repository through openharmony.gitee.com/openharmony/
by Christopher Tom 26 Oct '20

26 Oct '20

For the past few days I haven't been able to access https://openharmony.gitee.com/openharmony/ either through the website or repo/git. I can connect to the website at https://gitee.com/openharmony/ and after changing the 3rd line of .repo/manifests/default.xml from <remote fetch="https://openharmony.gitee.com/openharmony/" name="origin" review="https://openharmony.gitee.com/openharmony/"/> to <remote fetch="https://gitee.com/openharmony/" name="origin" review="https://openharmony.gitee.com/openharmony/"/> I can sync with repo (and faster than openharmony.gitee.com/openharmony/ was). But the manifest seems to still be pointing at openharmony.gitee.com/openharmony/, is anyone else having problems accessing the repository? Am I doing something wrong?

1 0