실험적으로 나온 결과를 N으로 나눠줘서 쓰고 있었는데
퍼시발의 규칙에 의해 개별 주파수의 진폭은 N개의 샘플에 의해 영향을 받게되고
진폭을 N으로 나누어 평준화해야 한다고 하는데 솔찍히 확 와닫는 소리는 아니다 -_ㅠ
[링크 : https://stackoverflow.com/questions/63211851/why-divide-the-output-of-numpy-fft-by-n]
[링크 : https://stackoverflow.com/questions/4855958/normalising-fft-data-fftw]
| FFT RBW (0) | 2023.09.19 |
|---|---|
| tek.com fft 관련 문서 (0) | 2023.07.19 |
| sfft (0) | 2023.07.12 |
| fft window type과 진폭 보정계수 (0) | 2023.07.04 |
| fft window 함수 (0) | 2023.07.03 |
라고 하는게 맞는진 모르겠지만
500개의 데이터를 1초에 샘플링 할 경우
500개의 데이터를 넣냐
100개의 데이터를 넣냐에 따라 나오는결과가 달라지는데 이걸 어떻게 해석하냐에 대한 내용
input data
|
for ( i = 0; i < n; i++ )
{
in[i] = ( double ) sin ( 2.0f * PI * (double)(i * 10) / n);
}
|
500 에 10 주기 니까 500SPS일 경우 10Hz에 peak가 떠야 한다.
500개를 다 넣으면 10Hz 에서 peak가 뜬다.
같은 애를 x축 크기만 조정해서 출력하면 아래처럼 보인다. (오른쪽은 왼쪽의 그래프를 X축에 대해서 5배 확대한 것)
 |
 |
100개만 넣어서 돌리면, 값은 50개만 나오고(100/2+1) peak는 2에서 나온다.
같은 애를 x축 크기만 조정해서 출력하면 아래처럼 보인다. (왼쪽은 오른쪽의 그래프를 X축에 대해서 1/5배로 축소한 것)
 |
 |
상관관계로 보면
샘플링 속도는 동일하고
데이터 갯수가 1/N 만큼 줄어들면
원래 주파수로 환원하기 위해서는 *N을 해야 한다.
위의 경우 1/5 였으니까
주파수는 *5를 해야 정상적으로 나오고
다르게 해석하면 5Hz 의 RBW로 분석 주파수 해상도가 낮아졌다 라고 표현하면 될 듯.
| fft 결과에 N(입력 샘플 갯수)로 나누는 이유 (0) | 2023.09.21 |
|---|---|
| tek.com fft 관련 문서 (0) | 2023.07.19 |
| sfft (0) | 2023.07.12 |
| fft window type과 진폭 보정계수 (0) | 2023.07.04 |
| fft window 함수 (0) | 2023.07.03 |
윈도우와는 다르게 리눅스에서는
HDMI + touch를 연결하면 자꾸 0번 디스플레이와 새로 연결된 터치가 연결된다.
윈도우에서 지금까진 안맞는적은 없었는데, 연결방법 글이 있는걸 보면 아주 없진 않나보다.
아무튼 윈도우는 어떤 시나리오로 되길래 외부 모니터와 touch를 잘 매칭해주는진 모르겠지만
[링크 : https://comterman.tistory.com/2738]
wayland 나 x.org 에서는 영~ 매칭이 잘 안된다.
화면 찢어짐 때문에 wayland로 해놨는데 그 여파로 따라해봐도 스크린에 터치가 옮겨가진 않는다.
[링크 : https://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor]
libinput-device.c를 보면 아래 함수 두개에 associated 용어를 표현하며
입력 장치를 evdev의 이벤트를 통해 연결하는데, 회사에서 시험해볼때는
touch 장치 쪽에서 연결할 스크린 명칭을 넣어주지 않아서인지 제대로 연결되는걸 못 본 듯.
|
void
evdev_device_set_calibration(struct evdev_device *device)
{
struct udev *udev;
struct udev_device *udev_device = NULL;
const char *sysname = libinput_device_get_sysname(device->device);
const char *calibration_values;
uint32_t width, height;
struct weston_touch_device_matrix calibration;
if (!libinput_device_config_calibration_has_matrix(device->device))
return;
/* If LIBINPUT_CALIBRATION_MATRIX was set to non-identity, we will not
* override it with WL_CALIBRATION. It also means we don't need an
* output to load a calibration. */
if (libinput_device_config_calibration_get_default_matrix(
device->device,
calibration.m) != 0)
return;
/* touch_set_calibration() has updated the values, do not load old
* values from WL_CALIBRATION.
*/
if (device->override_wl_calibration)
return;
if (!device->output) {
weston_log("input device %s has no enabled output associated "
"(%s named), skipping calibration for now.\n",
sysname, device->output_name ?: "none");
return;
}
void
evdev_device_set_output(struct evdev_device *device,
struct weston_output *output)
{
if (device->output == output)
return;
if (device->output_destroy_listener.notify) {
wl_list_remove(&device->output_destroy_listener.link);
device->output_destroy_listener.notify = NULL;
}
if (!output) {
weston_log("output for input device %s removed\n",
libinput_device_get_sysname(device->device));
device->output = NULL;
return;
}
weston_log("associating input device %s with output %s "
"(%s by udev)\n",
libinput_device_get_sysname(device->device),
output->name,
device->output_name ?: "none");
device->output = output;
device->output_destroy_listener.notify = notify_output_destroy;
wl_signal_add(&output->destroy_signal,
&device->output_destroy_listener);
evdev_device_set_calibration(device);
}
|
| wayland atomic commit 패치? (0) | 2022.08.22 |
|---|---|
| weston screen shooter 뜯어보기 (0) | 2022.08.17 |
| wayland glreadpixels 실패 (0) | 2022.08.16 |
| sway + wayvnc (0) | 2022.08.10 |
| wayvnc 0.5 릴리즈 (0) | 2022.08.09 |
전체는 아니고 weston 쪽을 기준으로 빌드하는데
소요시간이 1시간
| real 62m37.028s user 0m6.099s sys 0m0.797s |
나중에 노트북에서 다시 빌드해 봐야하나?
어째 i7-10510U+ nvme 보다
i5-3570 + sata ssd 가 더 빠른것 같은건 왜지..
데스크탑과 노트북이라 차이가 있긴 해도
벤치상으로는 노트북쪽이 신형이라 빠를텐데..?
| bitbake --help (0) | 2023.08.29 |
|---|---|
| Do not use Bitbake as root. (0) | 2023.08.28 |
| imx8 yocto (0) | 2023.08.28 |
| imx8 yocto build on ubuntu 22.04 (0) | 2023.02.10 |
| 라즈베리 파이 with yocto project (2) | 2015.07.30 |
wireshark 에서 any 인터페이스로 잡으면
linux cooked capture 라는 희한한(?) 레이어가 생긴다.
물론 wlo나 eth 와 같이 인터페이스를 지정하면 Ethernet II 이런식으로 뜬다.
[링크 : https://byeo.tistory.com/entry/Linux-Cooked-Capture-SLL-protocol]
| wireshark에서 DHCP 캡쳐하기 (0) | 2011.10.05 |
|---|---|
| wireshark(ethereal / 이더리얼)에서 특정 프로토콜만 필터하기 (0) | 2009.07.05 |
| ubuntu에 ethereal(wireshark) 설치하기 (0) | 2009.07.04 |
| ethereal -> wireshark (0) | 2009.07.04 |
엥...
라즈베리 파이 3B 64bit OS 에서는 잘 실행되는데
| pi@raspberrypi:~ $ mpirun -------------------------------------------------------------------------- mpirun could not find anything to do. It is possible that you forgot to specify how many processes to run via the "-np" argument. -------------------------------------------------------------------------- pi@raspberrypi:~ $ mpirun --version mpirun (Open MPI) 4.1.0 Report bugs to http://www.open-mpi.org/community/help/ |
odroid c2 에서는(aarch64) 에러가 난다
| $ mpirun Illegal instruction $ mpirun --help Illegal instruction $ mpirun --version mpirun (Open MPI) 4.0.3 Report bugs to http://www.open-mpi.org/community/help/ |
strace라던가 써서 추적해보려는데 패키지가 되먹질 않으니 짜증나네 -_ㅠ
odroid c2
| geteuid() = 1000 openat(AT_FDCWD, "/proc/cpuinfo", O_RDONLY) = 3 --- SIGILL {si_signo=SIGILL, si_code=ILL_ILLOPC, si_addr=0x7fa18b7cfc} --- +++ killed by SIGILL +++ Illegal instruction |
라즈베리 파이
| geteuid() = 1000 openat(AT_FDCWD, "/proc/cpuinfo", O_RDONLY) = 3 close(3) = 0 getuid() = 1000 geteuid() = 1000 |
도대체 고작 /proc/cpuinfo 여는걸로 죽다니 머지?
+
gdb로 해보니 뜬금없이 libopen-pal.so.40 에서 죽는다. 도대체 PAL 이 멀하는데 illegal instruction 을 띄울 작업을 하는거지?
| $ gdb mpirun GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from mpirun... (No debugging symbols found in mpirun) (gdb) r Starting program: /usr/bin/mpirun [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". Program received signal SIGILL, Illegal instruction. 0x0000007fb7ec5cfc in ?? () from /usr/lib/aarch64-linux-gnu/libopen-pal.so.40 |
눈이 이상해졌나 open-pam 인 줄.. -_-
아무튼 libopen-pal 혹은 OPAL 이라는 녀석이 현재 문제인데
openmpi는 liboshmem(shared memory 관리?) libmpi 그리고 libopen-pal로 구성된다고 한다.
| That is, they are compiled into separate libraries: liboshmem, libmpi, libopen-pal with a strict dependency order: OSHMEM depends on OMPI, OMPI depends on OPAL. |
[링크: https://docs.open-mpi.org/en/v5.0.x/developers/terminology.html]
open PAL은 체크포인트 와 프로그램 재시작을 할 수 있도록 해주는 녀석이니..
프로세서에 대해서 잘 알아야 프로그램을 멈추고 실행하게 할테니..
반대로 생각하면 odroid-c2에서 적용된 aarch64 버전이 amlogic 기반의 ap와는 맞지 않게 빌드된걸려나?
| Open PAL can involuntarily checkpoint and restart sequential programs. Doing so requires that Open PAL was compiled with thread support and that the back-end checkpointing systems are available at run-time. |
[링크 : https://www.open-mpi.org/doc/v4.1/man7/opal_crs.7.php]
+
odroid c2 에서 make -j4 로 openmpi-4.1.0 빌드에 걸린시간
중간에 gdb 설치한다고 순수하게 돌리면 24분쯤으로 되지 않았을까?
| real 25m20.199s user 52m9.680s sys 5m27.920s |
+
빡세게(?) 빌드까지 해서 겨우겨우 돌렸는데 왜 저런 에러가 또 나냐고 ㅠㅠ
| Program received signal SIGILL, Illegal instruction. 0x0000007fb7ec236c in opal_timer_linux_find_freq () from /usr/local/lib/libopen-pal.so.40 |
에러를 보니 먼가 함수명이 나와서 추적
| $ grep -rn "opal_timer_linux_find_freq" . Binary file ./opal/mca/timer/linux/.libs/timer_linux_component.o matches Binary file ./opal/mca/timer/linux/.libs/libmca_timer_linux.a matches ./opal/mca/timer/linux/timer_linux_component.c:105:static int opal_timer_linux_find_freq(void) ./opal/mca/timer/linux/timer_linux_component.c:203: ret = opal_timer_linux_find_freq(); $ cat opal/mca/timer/linux/timer_linux_component.c static int opal_timer_linux_find_freq(void) { FILE *fp; char *loc; float cpu_f; int ret; char buf[1024]; fp = fopen("/proc/cpuinfo", "r"); if (NULL == fp) { return OPAL_ERR_IN_ERRNO; } opal_timer_linux_freq = 0; #if OPAL_ASSEMBLY_ARCH == OPAL_ARM64 opal_timer_linux_freq = opal_sys_timer_freq(); #endif $ grep -rni "opal_sys_timer_freq" . ./mca/timer/linux/timer_linux_component.c:121: opal_timer_linux_freq = opal_sys_timer_freq(); ./include/opal/sys/arm64/timer.h:36:opal_sys_timer_freq(void) $ cat openmpi-4.1.0/opal/include/opal/sys/arm64/timer.h static inline opal_timer_t opal_sys_timer_freq(void) { opal_timer_t freq; __asm__ __volatile__ ("mrs %0, CNTFRQ_EL0" : "=r" (freq)); return (opal_timer_t)(freq); } |
레지스터 이름부터가 무시무시하네?
| MRS Move System Register. Syntax MRS Xt, (systemreg|Sop0_op1_Cn_Cm_op2) Where: Xt Is the 64-bit name of the general-purpose destination register. systemreg Is a System register name. The System register names are defined in 'AArch64 System Registers' in the System Register XML. op0 Is an unsigned immediate, and can be either 2 or 3. op1 Is a 3-bit unsigned immediate, in the range 0 to 7. Cn Is a name Cn, with n in the range 0 to 15. Cm Is a name Cm, with m in the range 0 to 15. op2 Is a 3-bit unsigned immediate, in the range 0 to 7. Usage Move System Register allows the PE to read an AArch64 System register into a general-purpose register. |
[링크 : https://developer.arm.com/documentation/dui0801/h/A64-General-Instructions/MRS]
| Accessing CNTFRQ_EL0 Accesses to this register use the following encodings in the System register encoding space: MRS <Xt>, CNTFRQ_EL0 op0 |
| The two instructions you show above are therefore - MSR HPFAR_EL2, X0 MSR PSTATEField_SP, #0 |
[링크 : https://reverseengineering.stackexchange.com/questions/14617/arm-understanding-msr-mrs-instructions]
보면.. uboot에도 있는 아주 평범한(?) 녀석인데.. 머지?
| unsigned long timer_read_counter(void) { unsigned long cntpct; unsigned long temp; isb(); asm volatile("mrs %0, cntpct_el0" : "=r" (cntpct)); asm volatile("mrs %0, cntpct_el0" : "=r" (temp)); while (temp != cntpct) { asm volatile("mrs %0, cntpct_el0" : "=r" (cntpct)); asm volatile("mrs %0, cntpct_el0" : "=r" (temp)); } return cntpct; } |
[링크 : https://github.com/qemu/u-boot/blob/master/arch/arm/cpu/armv8/generic_timer.c]
%0은 이전의 dst 를 의미하는걸려나?
| int val = 50; __asm volatile ("MOV R0, %0": : "r"(var) ); ==> (컴파일러 해석) ldr r3, [r7, #4] mov r0, r3 |
[링크 : https://dhpark1212.tistory.com/entry/ARM-GCC-Inline-assembly-coding]
amlogic 의 Cortex-A53인데 많이 다른가?
| ODROID-C2 | ODROID-C1+ | RPi 3 Model B | |
| CPU |
Amlogic S905 SoC
4 x ARM Cortex-A53 1.5GHz
64bit ARMv8 Architecture @28nm
|
Amlogic S805 SoC
4 x ARM Cortex-A5 1.5GHz
32bit ARMv7 Architecture @28nm
|
Broadcom BCM2837
4 x ARM Cortex-A53 1.2Ghz
64bit ARMv7 Architecture @40nm
|
| openFOAM + freecad + salome (0) | 2023.06.07 |
|---|---|
| openFOAM tutorial with youtube (0) | 2023.05.24 |
| openfoam on ubuntu (0) | 2023.05.24 |
| openFOAM tutorial (2) | 2023.05.24 |
| openfoam7 on ubuntu 18.04 (0) | 2020.08.09 |
freecad 에서 도면을 그리려면 먼가 어렵다?
상단의 툴바에서 누르던가 아니면
보기 - 워크벤치 - Draft 혹은 Part Design을 누르면 되는 것 같은데
Draft를 누르면 아래와 같이 격자종이가 나오고
part Design을 누르면 그냥 빈화면만 나온다.
[링크 : https://commox111.tistory.com/65]
part design 에서 점이나 선을 그리려면 활성바디가 없다고 에러가 나는데
좌측에 생성 : 바디(body) 누르면 어떻게 시작은 가능한 듯.
[링크 : https://www.youtube.com/watch?v=x53Jbr16ekI]
아무튼 draft 에서 대충대충 선을 그리고
modification - array tools - circular array로 대충 베어링은 그려볼 수 있을 듯.
| ubuntu용 cad 프로그램 (0) | 2020.09.23 |
|---|---|
| freecad 설명 (0) | 2018.01.22 |
명령어 조사중
bitbake -c compile -f recipe 식으로 많이 써왔는데
상세 명령이나 recipre 목록등을 얻는 방법을 찾는 중
| Usage: bitbake [options] [recipename/target recipe:do_task ...] Executes the specified task (default is 'build') for a given set of target recipes (.bb files). It is assumed there is a conf/bblayers.conf available in cwd or in BBPATH which will provide the layer, BBFILES and other configuration information. Options: --version show program's version number and exit -h, --help show this help message and exit -b BUILDFILE, --buildfile=BUILDFILE Execute tasks from a specific .bb recipe directly. WARNING: Does not handle any dependencies from other recipes. -k, --continue Continue as much as possible after an error. While the target that failed and anything depending on it cannot be built, as much as possible will be built before stopping. -f, --force Force the specified targets/task to run (invalidating any existing stamp file). -c CMD, --cmd=CMD Specify the task to execute. The exact options available depend on the metadata. Some examples might be 'compile' or 'populate_sysroot' or 'listtasks' may give a list of the tasks available. -C INVALIDATE_STAMP, --clear-stamp=INVALIDATE_STAMP Invalidate the stamp for the specified task such as 'compile' and then run the default task for the specified target(s). -r PREFILE, --read=PREFILE Read the specified file before bitbake.conf. -R POSTFILE, --postread=POSTFILE Read the specified file after bitbake.conf. -v, --verbose Enable tracing of shell tasks (with 'set -x'). Also print bb.note(...) messages to stdout (in addition to writing them to ${T}/log.do_<task>). -D, --debug Increase the debug level. You can specify this more than once. -D sets the debug level to 1, where only bb.debug(1, ...) messages are printed to stdout; -DD sets the debug level to 2, where both bb.debug(1, ...) and bb.debug(2, ...) messages are printed; etc. Without -D, no debug messages are printed. Note that -D only affects output to stdout. All debug messages are written to ${T}/log.do_taskname, regardless of the debug level. -q, --quiet Output less log message data to the terminal. You can specify this more than once. -n, --dry-run Don't execute, just go through the motions. -S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER Dump out the signature construction information, with no task execution. The SIGNATURE_HANDLER parameter is passed to the handler. Two common values are none and printdiff but the handler may define more/less. none means only dump the signature, printdiff means compare the dumped signature with the cached one. -p, --parse-only Quit after parsing the BB recipes. -s, --show-versions Show current and preferred versions of all recipes. -e, --environment Show the global or per-recipe environment complete with information about where variables were set/changed. -g, --graphviz Save dependency tree information for the specified targets in the dot syntax. -I EXTRA_ASSUME_PROVIDED, --ignore-deps=EXTRA_ASSUME_PROVIDED Assume these dependencies don't exist and are already provided (equivalent to ASSUME_PROVIDED). Useful to make dependency graphs more appealing -l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS Show debug logging for the specified logging domains -P, --profile Profile the command and save reports. -u UI, --ui=UI The user interface to use (knotty, ncurses or teamcity - default knotty). --token=XMLRPCTOKEN Specify the connection token to be used when connecting to a remote server. --revisions-changed Set the exit code depending on whether upstream floating revisions have changed or not. --server-only Run bitbake without a UI, only starting a server (cooker) process. -B BIND, --bind=BIND The name/address for the bitbake xmlrpc server to bind to. -T SERVER_TIMEOUT, --idle-timeout=SERVER_TIMEOUT Set timeout to unload bitbake server due to inactivity, set to -1 means no unload, default: Environment variable BB_SERVER_TIMEOUT. --no-setscene Do not run any setscene tasks. sstate will be ignored and everything needed, built. --skip-setscene Skip setscene tasks if they would be executed. Tasks previously restored from sstate will be kept, unlike --no-setscene --setscene-only Only run setscene tasks, don't run any real tasks. --remote-server=REMOTE_SERVER Connect to the specified server. -m, --kill-server Terminate any running bitbake server. --observe-only Connect to a server as an observing-only client. --status-only Check the status of the remote bitbake server. -w WRITEEVENTLOG, --write-log=WRITEEVENTLOG Writes the event log of the build to a bitbake event json file. Use '' (empty string) to assign the name automatically. --runall=RUNALL Run the specified task for any recipe in the taskgraph of the specified target (even if it wouldn't otherwise have run). --runonly=RUNONLY Run only the specified task within the taskgraph of the specified targets (and any task dependencies those tasks may have). |
| $ bitbake -c listtasks Nothing to do. Use 'bitbake world' to build everything, or run 'bitbake --help' for usage information. |
| $ bitbake-layers show-recipes |
| For an updated list for a specific recipe, run: bitbake -c listtasks <recipe> fetchall Fetch all source build devshell package_write_ipk cleansstate Clean the build/sstate-cache directory configure clean clean $WORKDIR cleanall clean $WORKDIR and sstate-cache populate_lic package_write populate_sysroot buildall populate_lic_setscene patch listtasks list all tasks that can be run for a target compile package_setscene fetch checkuri package_write_ipk_setscene package unpack install populate_sysroot_setscene checkuriall |
[링크 : https://www.openembedded.org/wiki/List_of_Executable_tasks]
| yocto build on i5-3570 (0) | 2023.09.07 |
|---|---|
| Do not use Bitbake as root. (0) | 2023.08.28 |
| imx8 yocto (0) | 2023.08.28 |
| imx8 yocto build on ubuntu 22.04 (0) | 2023.02.10 |
| 라즈베리 파이 with yocto project (2) | 2015.07.30 |
bitbake로 yocto를 빌드 하려고 하는데 에러가 나서 찾아보니
메시지 자체는 root로 bitbake 하지 말란건데, 설정상으로는 sanity를 inherit 하지 않도록 하면 되는 듯.
분별을(제정신을) 상속 안받으면 제정신이 아니게 되는건가...(!)
| sanity 미국∙영국 [ˈsænəti] 영국식 1. [명사] 온전한 정신 (상태) 2. [명사] 분별 (→sane), (↔insanity) |
| # Sanity checks for common user misconfigurations # # See sanity.bbclass # # Expert users can confirm their sanity with "touch conf/sanity.conf" BB_MIN_VERSION = "1.49.2" SANITY_ABIFILE = "${TMPDIR}/abi_version" SANITY_VERSION ?= "1" LOCALCONF_VERSION ?= "1" LAYER_CONF_VERSION ?= "7" SITE_CONF_VERSION ?= "1" #INHERIT += "sanity" |
| yocto build on i5-3570 (0) | 2023.09.07 |
|---|---|
| bitbake --help (0) | 2023.08.29 |
| imx8 yocto (0) | 2023.08.28 |
| imx8 yocto build on ubuntu 22.04 (0) | 2023.02.10 |
| 라즈베리 파이 with yocto project (2) | 2015.07.30 |
문서가 개정되어서 하기 쉽게 잘 나와있는 듯.
| Rev. LF6.1.22_2.0.0 — 30 June 2023 The recommended minimum Ubuntu version is 20.04 or later. $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev python3- subunit mesa-common-dev zstd liblz4-tool file locales // lz4c 어쩌구 나오면 $ sudo apt install lz4 // repo 설치 $ mkdir ~/bin (this step may not be needed if the bin folder already exists) $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repo // repo 초기화 $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-mickledore -m imx-6.1.22-2.0.0.xml $ repo sync $ DISTRO=<distro name> MACHINE=<machine name> source imx-setup-release.sh -b <build dir> $ bitbake imx-image-multimedia |
[링크 : https://www.nxp.com/docs/en/user-guide/IMX_YOCTO_PROJECT_USERS_GUIDE.pdf]
python 패키지 명이 바뀌어서 손을 대보는데 그래도 안되서
혹시나 하는 마음에 3.9를 설치해보니 정상적으로 설치안되었다고 -_-
| $ bitbake -c compile -f weston Traceback (most recent call last): File "/home/falinux/work/work/yocto/sources/poky/bitbake/bin/bitbake", line 19, in <module> import bb File "/home/falinux/work/work/yocto/sources/poky/bitbake/lib/bb/__init__.py", line 128, in <module> from bb import fetch2 as fetch File "/home/falinux/work/work/yocto/sources/poky/bitbake/lib/bb/fetch2/__init__.py", line 26, in <module> import bb.persist_data, bb.utils File "/home/falinux/work/work/yocto/sources/poky/bitbake/lib/bb/persist_data.py", line 22, in <module> from collections import Mapping ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) $ bitbake -c compile -f weston WARNING: Host distribution "ubuntu-22.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Your Python 3 is not a full install. Please install the module distutils.sysconfig (see the Getting Started guide for further information). Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. |
3.10 부터 패키지 명칭이 바뀌어서 그런일이 생기는 듯
| For version 3.10 or above – from collections.abc import MutableMapping For version 3.9 or lower – from collections import MutableMapping |
+
걍 docker 쓸까..
| bitbake --help (0) | 2023.08.29 |
|---|---|
| Do not use Bitbake as root. (0) | 2023.08.28 |
| imx8 yocto build on ubuntu 22.04 (0) | 2023.02.10 |
| 라즈베리 파이 with yocto project (2) | 2015.07.30 |
| yocto project 구조 (0) | 2015.07.29 |
|
