telnet 등을 접속하는데 utf-8 이 아닌 경우 해당 인코딩을 바꾸어서 보여주는 유틸리티
| -encoding encoding Set up luit to use encoding rather than the current locale's encoding. |
[링크 : https://linux.die.net/man/1/luit]
| ubuntu 22.04 bgr 패널 대응 (0) | 2025.12.29 |
|---|---|
| clamav (0) | 2025.12.22 |
| evince (리눅스 pdf 뷰어) 네비게이션 (0) | 2025.12.11 |
| ubuntu 22.04 bgr subpixel 대응 찾기 실패 (0) | 2025.11.25 |
| ts - moreutils (0) | 2025.09.26 |
아니 저런(?) 쓸데없는걸 그려주는 좋은 클래스가 있다니 ㅋ
[링크 : https://doc.qt.io/qt-6/ko/qlcdnumber.html#details]
그 와중에 qt creator 에서 widget으로 제공된다.
프로퍼티가 제법 많다.
소수점 자리는 지정할수 있는데, 아쉽게도(?) 자릿수 까진 없는 듯.
| qt qrc 리소스 등록 후 이미지로 띄우기 (0) | 2026.03.23 |
|---|---|
| qt 6 프로그래밍 공개 ebook (0) | 2026.03.23 |
| QT QWizard (0) | 2026.03.19 |
| qt widget 화면 전환 (0) | 2026.03.18 |
| qt qml 와 c++ 상호연동 (0) | 2026.01.16 |
일단 button에 icon 으로 하는 방법과
label을 등록하고 pixmap 으로 등록하는 방법이 qt creator / qt widget designer 에서 마우스로 쉽게 할 수 있는 방법인듯
QButton
[링크 : https://coding-chobo.tistory.com/40]
QLabel
[링크 : https://1d1cblog.tistory.com/37]
[링크 : https://blog.naver.com/hextrial/221109232458]
[링크 : https://stackoverflow.com/questions/5653114/display-image-in-qt-to-fit-label-size]
| QLCDNumber class (0) | 2026.03.23 |
|---|---|
| qt 6 프로그래밍 공개 ebook (0) | 2026.03.23 |
| QT QWizard (0) | 2026.03.19 |
| qt widget 화면 전환 (0) | 2026.03.18 |
| qt qml 와 c++ 상호연동 (0) | 2026.01.16 |
| QLCDNumber class (0) | 2026.03.23 |
|---|---|
| qt qrc 리소스 등록 후 이미지로 띄우기 (0) | 2026.03.23 |
| QT QWizard (0) | 2026.03.19 |
| qt widget 화면 전환 (0) | 2026.03.18 |
| qt qml 와 c++ 상호연동 (0) | 2026.01.16 |
2023년 6월 9일 단종 공고가 떴었다.
그럼 quartus도 22.x 까지만 지원할 것 같은데. 아예 사라진건진 봐야 알 듯.
[링크 : https://www.reddit.com/r/FPGA/comments/1492bx0/intel_discontinues_nios_ii_ip/]
nios v/m nios v/g 로 대체라면 기존의 ii/e ii/f 중에 f가 바뀌나?
ipr-nios가 정식으로 쓰는거고 ip-nios는 evaluation 이라는데(1시간 이후 멈춤) 맞나?
그나저나 DMIPS 드럽게 낮네
STM32F102x8 cortex-m3의 경우 1.25DMIPS 라는데 시기가 차이 있다 하더라도 nios ii/f가 제법 처참하다 싶다.
1.25 DMIPS/MHz (Dhrystone 2.1)
[링크 : https://www.st.com/resource/en/datasheet/stm32f102c8.pdf]
17년 이후로 Nios ii gen 2로 바뀌면서 nios ii/s는 사라지고 f만 남은거 같은데
그러면 위에 ip-nios랑 ipr-nios는 f인가? 머지?
Nios II classic is offered in 3 different configurations: Nios II/f (fast), Nios II/s (standard), and Nios II/e (economy). Nios II gen2 is offered in 2 different configurations: Nios II/f (fast), and Nios II/e (economy).Nios II/f
Nios II/s
Nios II/e |
[링크 : https://en.wikipedia.org/wiki/Nios_II]
+
ai 답변
quartus 19.1 부터 EDS 제거되면서 윈도우에서 WSL 필요
quartus 24.1 부터 nios ii / eds 제거
+
레딧도 그렇지만 정말 취미(?) 사용자를 위해서는 두 회사가 더 멀어지고 있지만
altera는 intel에 인수되면서 더 심화된것 같고. 그래서 altera가 다시 intel과 결별한게 아닌가 싶다.
[링크 : https://www.cio.com/article/3964395/인텔-알테라-지분-51-매각···-fpga-사업-정리해-구조-개.html]
이 추세면.. xilinx로 갈아타야 하려나.. 쩝..
terasic 형님들 de0-nano-soc 처럼 쌈박한 zynq 내주실 생각 없습니까!?!??!
| de1-soc system builder 에서 hps 추가 후 빌드 실패 (0) | 2026.03.21 |
|---|---|
| fpga sdk for openCL (0) | 2026.03.18 |
| aocl_c5soc_getting_started.pdf (Altera SDK for OpenCL) (0) | 2026.03.18 |
| de1-soc와 quartus / fpga sdk for opencl (0) | 2026.03.18 |
| quartus prime standard 실행 (0) | 2026.03.17 |
찾아보니 원래 한 40만원 하던걸
비 맞고 수리비가 더 들어서 수리없이 5만원에 자전거 매장에서 중고로 업어옴
그래도 무려 티티카카 tube a7 이라 네임벨류가 있는 ㅋㅋ
아니.. HPS 넣으면 IP에서 추가하라고 말만하지 말고
좀 강하게 경고를 하라고 ㅠㅠ
quartus 에서 넣으면 되는줄 알았는데 그게 아니고
tools - platform designer 해서 넣어야 하나보다.(까먹어서 인터넷 검색..)
먼가 복잡하게 뜨는데 먼지 모르니 귀찮아서(!) finish 하고
clk 와 각종 clock_input들을 O를 클릭해서 검은색이 체크되어 클럭이 넘어오게 해주고
종료하려고 하면 Generate Now? 라고 물어보는데 이걸 "예" 하던가
platform designed의 우측 하단 Generate HDL을 누르면 될 듯.
그리고 Finish 해주면 먼가
아까는 안보이던 hps가 추가되어있는데
이걸 더블클릭해서 먼가 또 이상한짓을 하고 나면 되는 듯?
그리고 뜨는 다이얼로그를 보니 수동으로 추가해야 하나는 것 같다.
project nabigaor를 file로 하고 우클릭한다음 "Add/Remove Files in Project" 해서
설정 창이 열리면 File name ... 을 눌러서
qip 확장자를 찾아서 넣고
빌드해도 안되네!!!
아우 빡셔.. 튜토리얼 다시 찾아봐야겠다.
+
지금은 Bidir로 되어있는데
이미 생성되어있는 프로젝트 열어서 보니 엥 Unknown?
readonly 라고 수정도 안되는데 어우.. 어떻게 하지 ㅠㅠ
+
2026.03.22
아래껄 추가하니 조금더 진행은 되는데
| unnamed u0 ( .clk_clk ( CLOCK_50), // clk.clk .reset_reset_n ( 1'b1), // reset.reset_n .memory_mem_a ( HPS_DDR3_ADDR), // memory.mem_a .memory_mem_ba ( HPS_DDR3_BA), // .mem_ba .memory_mem_ck ( HPS_DDR3_CK_P), // .mem_ck .memory_mem_ck_n ( HPS_DDR3_CK_N), // .mem_ck_n .memory_mem_cke ( HPS_DDR3_CKE), // .mem_cke .memory_mem_cs_n ( HPS_DDR3_CS_N), // .mem_cs_n .memory_mem_ras_n ( HPS_DDR3_RAS_N), // .mem_ras_n .memory_mem_cas_n ( HPS_DDR3_CAS_N), // .mem_cas_n .memory_mem_we_n ( HPS_DDR3_WE_N), // .mem_we_n .memory_mem_reset_n ( HPS_DDR3_RESET_N), // .mem_reset_n .memory_mem_dq ( HPS_DDR3_DQ), // .mem_dq .memory_mem_dqs ( HPS_DDR3_DQS_P), // .mem_dqs .memory_mem_dqs_n ( HPS_DDR3_DQS_N), // .mem_dqs_n .memory_mem_odt ( HPS_DDR3_ODT), // .mem_odt .memory_mem_dm ( HPS_DDR3_DM), // .mem_dm .memory_oct_rzqin ( HPS_DDR3_RZQ), // .oct_rzqin }; |
또 먼가 잘못했는지 -_-
여전히 DDR3쪽 DQS 핀 에러는 여전하고
그 와중에 용량이 부족하다고 배째는데 이게 말이... 되나?
| Error (169008): Can't turn on open-drain option for differential I/O pin HPS_DDR3_DQS_N[1] Error (169008): Can't turn on open-drain option for differential I/O pin HPS_DDR3_DQS_N[2] Error (169008): Can't turn on open-drain option for differential I/O pin HPS_DDR3_DQS_N[3] Error (169008): Can't turn on open-drain option for differential I/O pin HPS_DDR3_DQS_P[1] Error (169008): Can't turn on open-drain option for differential I/O pin HPS_DDR3_DQS_P[2] Error (169008): Can't turn on open-drain option for differential I/O pin HPS_DDR3_DQS_P[3] Info (11798): Fitter preparation operations ending: elapsed time is 00:00:00 Warning (169064): Following 85 pins have no output enable or a GND or VCC output enable - later changes to this connectivity may change fitting results Info (169065): Pin AUD_ADCLRCK has a permanently disabled output enable Info (169065): Pin AUD_BCLK has a permanently disabled output enable Info (169065): Pin AUD_DACLRCK has a permanently disabled output enable Info (169065): Pin DRAM_DQ[0] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[1] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[2] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[3] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[4] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[5] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[6] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[7] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[8] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[9] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[10] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[11] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[12] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[13] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[14] has a permanently disabled output enable Info (169065): Pin DRAM_DQ[15] has a permanently disabled output enable Info (169065): Pin FPGA_I2C_SDAT has a permanently disabled output enable Info (169065): Pin PS2_CLK has a permanently disabled output enable Info (169065): Pin PS2_CLK2 has a permanently disabled output enable Info (169065): Pin PS2_DAT has a permanently disabled output enable Info (169065): Pin PS2_DAT2 has a permanently disabled output enable Info (169065): Pin HPS_CONV_USB_N has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[8] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[9] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[10] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[11] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[12] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[13] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[14] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[15] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[16] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[17] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[18] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[19] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[20] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[21] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[22] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[23] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[24] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[25] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[26] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[27] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[28] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[29] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[30] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQ[31] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQS_N[1] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQS_N[2] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQS_N[3] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQS_P[1] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQS_P[2] has a permanently disabled output enable Info (169065): Pin HPS_DDR3_DQS_P[3] has a permanently disabled output enable Info (169065): Pin HPS_ENET_INT_N has a permanently disabled output enable Info (169065): Pin HPS_ENET_MDIO has a permanently disabled output enable Info (169065): Pin HPS_FLASH_DATA[0] has a permanently disabled output enable Info (169065): Pin HPS_FLASH_DATA[1] has a permanently disabled output enable Info (169065): Pin HPS_FLASH_DATA[2] has a permanently disabled output enable Info (169065): Pin HPS_FLASH_DATA[3] has a permanently disabled output enable Info (169065): Pin HPS_GPIO[0] has a permanently disabled output enable Info (169065): Pin HPS_GPIO[1] has a permanently disabled output enable Info (169065): Pin HPS_GSENSOR_INT has a permanently disabled output enable Info (169065): Pin HPS_I2C1_SCLK has a permanently disabled output enable Info (169065): Pin HPS_I2C1_SDAT has a permanently disabled output enable Info (169065): Pin HPS_I2C2_SCLK has a permanently disabled output enable Info (169065): Pin HPS_I2C2_SDAT has a permanently disabled output enable Info (169065): Pin HPS_I2C_CONTROL has a permanently disabled output enable Info (169065): Pin HPS_KEY has a permanently disabled output enable Info (169065): Pin HPS_LED has a permanently disabled output enable Info (169065): Pin HPS_SD_CMD has a permanently disabled output enable Info (169065): Pin HPS_SD_DATA[0] has a permanently disabled output enable Info (169065): Pin HPS_SD_DATA[1] has a permanently disabled output enable Info (169065): Pin HPS_SD_DATA[2] has a permanently disabled output enable Info (169065): Pin HPS_SD_DATA[3] has a permanently disabled output enable Info (169065): Pin HPS_SPIM_SS has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[0] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[1] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[2] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[3] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[4] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[5] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[6] has a permanently disabled output enable Info (169065): Pin HPS_USB_DATA[7] has a permanently disabled output enable Warning (169069): Following 216 pins have nothing, GND, or VCC driving datain port -- changes to this connectivity may change fitting results Info (169070): Pin ADC_CONVST has GND driving its datain port Info (169070): Pin ADC_DIN has GND driving its datain port Info (169070): Pin ADC_SCLK has GND driving its datain port Info (169070): Pin AUD_DACDAT has GND driving its datain port Info (169070): Pin AUD_XCK has GND driving its datain port Info (169070): Pin DRAM_ADDR[0] has GND driving its datain port Info (169070): Pin DRAM_ADDR[1] has GND driving its datain port Info (169070): Pin DRAM_ADDR[2] has GND driving its datain port Info (169070): Pin DRAM_ADDR[3] has GND driving its datain port Info (169070): Pin DRAM_ADDR[4] has GND driving its datain port Info (169070): Pin DRAM_ADDR[5] has GND driving its datain port Info (169070): Pin DRAM_ADDR[6] has GND driving its datain port Info (169070): Pin DRAM_ADDR[7] has GND driving its datain port Info (169070): Pin DRAM_ADDR[8] has GND driving its datain port Info (169070): Pin DRAM_ADDR[9] has GND driving its datain port Info (169070): Pin DRAM_ADDR[10] has GND driving its datain port Info (169070): Pin DRAM_ADDR[11] has GND driving its datain port Info (169070): Pin DRAM_ADDR[12] has GND driving its datain port Info (169070): Pin DRAM_BA[0] has GND driving its datain port Info (169070): Pin DRAM_BA[1] has GND driving its datain port Info (169070): Pin DRAM_CAS_N has GND driving its datain port Info (169070): Pin DRAM_CKE has GND driving its datain port Info (169070): Pin DRAM_CLK has GND driving its datain port Info (169070): Pin DRAM_CS_N has GND driving its datain port Info (169070): Pin DRAM_LDQM has GND driving its datain port Info (169070): Pin DRAM_RAS_N has GND driving its datain port Info (169070): Pin DRAM_UDQM has GND driving its datain port Info (169070): Pin DRAM_WE_N has GND driving its datain port Info (169070): Pin FPGA_I2C_SCLK has GND driving its datain port Info (169070): Pin HEX0[0] has GND driving its datain port Info (169070): Pin HEX0[1] has GND driving its datain port Info (169070): Pin HEX0[2] has GND driving its datain port Info (169070): Pin HEX0[3] has GND driving its datain port Info (169070): Pin HEX0[4] has GND driving its datain port Info (169070): Pin HEX0[5] has GND driving its datain port Info (169070): Pin HEX0[6] has GND driving its datain port Info (169070): Pin HEX1[0] has GND driving its datain port Info (169070): Pin HEX1[1] has GND driving its datain port Info (169070): Pin HEX1[2] has GND driving its datain port Info (169070): Pin HEX1[3] has GND driving its datain port Info (169070): Pin HEX1[4] has GND driving its datain port Info (169070): Pin HEX1[5] has GND driving its datain port Info (169070): Pin HEX1[6] has GND driving its datain port Info (169070): Pin HEX2[0] has GND driving its datain port Info (169070): Pin HEX2[1] has GND driving its datain port Info (169070): Pin HEX2[2] has GND driving its datain port Info (169070): Pin HEX2[3] has GND driving its datain port Info (169070): Pin HEX2[4] has GND driving its datain port Info (169070): Pin HEX2[5] has GND driving its datain port Info (169070): Pin HEX2[6] has GND driving its datain port Info (169070): Pin HEX3[0] has GND driving its datain port Info (169070): Pin HEX3[1] has GND driving its datain port Info (169070): Pin HEX3[2] has GND driving its datain port Info (169070): Pin HEX3[3] has GND driving its datain port Info (169070): Pin HEX3[4] has GND driving its datain port Info (169070): Pin HEX3[5] has GND driving its datain port Info (169070): Pin HEX3[6] has GND driving its datain port Info (169070): Pin HEX4[0] has GND driving its datain port Info (169070): Pin HEX4[1] has GND driving its datain port Info (169070): Pin HEX4[2] has GND driving its datain port Info (169070): Pin HEX4[3] has GND driving its datain port Info (169070): Pin HEX4[4] has GND driving its datain port Info (169070): Pin HEX4[5] has GND driving its datain port Info (169070): Pin HEX4[6] has GND driving its datain port Info (169070): Pin HEX5[0] has GND driving its datain port Info (169070): Pin HEX5[1] has GND driving its datain port Info (169070): Pin HEX5[2] has GND driving its datain port Info (169070): Pin HEX5[3] has GND driving its datain port Info (169070): Pin HEX5[4] has GND driving its datain port Info (169070): Pin HEX5[5] has GND driving its datain port Info (169070): Pin HEX5[6] has GND driving its datain port Info (169070): Pin IRDA_TXD has GND driving its datain port Info (169070): Pin LEDR[0] has GND driving its datain port Info (169070): Pin LEDR[1] has GND driving its datain port Info (169070): Pin LEDR[2] has GND driving its datain port Info (169070): Pin LEDR[3] has GND driving its datain port Info (169070): Pin LEDR[4] has GND driving its datain port Info (169070): Pin LEDR[5] has GND driving its datain port Info (169070): Pin LEDR[6] has GND driving its datain port Info (169070): Pin LEDR[7] has GND driving its datain port Info (169070): Pin LEDR[8] has GND driving its datain port Info (169070): Pin LEDR[9] has GND driving its datain port Info (169070): Pin TD_RESET_N has GND driving its datain port Info (169070): Pin VGA_BLANK_N has GND driving its datain port Info (169070): Pin VGA_B[0] has GND driving its datain port Info (169070): Pin VGA_B[1] has GND driving its datain port Info (169070): Pin VGA_B[2] has GND driving its datain port Info (169070): Pin VGA_B[3] has GND driving its datain port Info (169070): Pin VGA_B[4] has GND driving its datain port Info (169070): Pin VGA_B[5] has GND driving its datain port Info (169070): Pin VGA_B[6] has GND driving its datain port Info (169070): Pin VGA_B[7] has GND driving its datain port Info (169070): Pin VGA_CLK has GND driving its datain port Info (169070): Pin VGA_G[0] has GND driving its datain port Info (169070): Pin VGA_G[1] has GND driving its datain port Info (169070): Pin VGA_G[2] has GND driving its datain port Info (169070): Pin VGA_G[3] has GND driving its datain port Info (169070): Pin VGA_G[4] has GND driving its datain port Info (169070): Pin VGA_G[5] has GND driving its datain port Info (169070): Pin VGA_G[6] has GND driving its datain port Info (169070): Pin VGA_G[7] has GND driving its datain port Info (169070): Pin VGA_HS has GND driving its datain port Info (169070): Pin VGA_R[0] has GND driving its datain port Info (169070): Pin VGA_R[1] has GND driving its datain port Info (169070): Pin VGA_R[2] has GND driving its datain port Info (169070): Pin VGA_R[3] has GND driving its datain port Info (169070): Pin VGA_R[4] has GND driving its datain port Info (169070): Pin VGA_R[5] has GND driving its datain port Info (169070): Pin VGA_R[6] has GND driving its datain port Info (169070): Pin VGA_R[7] has GND driving its datain port Info (169070): Pin VGA_SYNC_N has GND driving its datain port Info (169070): Pin VGA_VS has GND driving its datain port Info (169070): Pin HPS_DDR3_ADDR[13] has GND driving its datain port Info (169070): Pin HPS_DDR3_ADDR[14] has GND driving its datain port Info (169070): Pin HPS_DDR3_DM[1] has GND driving its datain port Info (169070): Pin HPS_DDR3_DM[2] has GND driving its datain port Info (169070): Pin HPS_DDR3_DM[3] has GND driving its datain port Info (169070): Pin HPS_ENET_GTX_CLK has GND driving its datain port Info (169070): Pin HPS_ENET_MDC has GND driving its datain port Info (169070): Pin HPS_ENET_TX_DATA[0] has GND driving its datain port Info (169070): Pin HPS_ENET_TX_DATA[1] has GND driving its datain port Info (169070): Pin HPS_ENET_TX_DATA[2] has GND driving its datain port Info (169070): Pin HPS_ENET_TX_DATA[3] has GND driving its datain port Info (169070): Pin HPS_ENET_TX_EN has GND driving its datain port Info (169070): Pin HPS_FLASH_DCLK has GND driving its datain port Info (169070): Pin HPS_FLASH_NCSO has GND driving its datain port Info (169070): Pin HPS_SD_CLK has GND driving its datain port Info (169070): Pin HPS_SPIM_CLK has GND driving its datain port Info (169070): Pin HPS_SPIM_MOSI has GND driving its datain port Info (169070): Pin HPS_UART_TX has GND driving its datain port Info (169070): Pin HPS_USB_STP has GND driving its datain port Info (169070): Pin AUD_ADCLRCK has VCC driving its datain port Info (169070): Pin AUD_BCLK has VCC driving its datain port Info (169070): Pin AUD_DACLRCK has VCC driving its datain port Info (169070): Pin DRAM_DQ[0] has VCC driving its datain port Info (169070): Pin DRAM_DQ[1] has VCC driving its datain port Info (169070): Pin DRAM_DQ[2] has VCC driving its datain port Info (169070): Pin DRAM_DQ[3] has VCC driving its datain port Info (169070): Pin DRAM_DQ[4] has VCC driving its datain port Info (169070): Pin DRAM_DQ[5] has VCC driving its datain port Info (169070): Pin DRAM_DQ[6] has VCC driving its datain port Info (169070): Pin DRAM_DQ[7] has VCC driving its datain port Info (169070): Pin DRAM_DQ[8] has VCC driving its datain port Info (169070): Pin DRAM_DQ[9] has VCC driving its datain port Info (169070): Pin DRAM_DQ[10] has VCC driving its datain port Info (169070): Pin DRAM_DQ[11] has VCC driving its datain port Info (169070): Pin DRAM_DQ[12] has VCC driving its datain port Info (169070): Pin DRAM_DQ[13] has VCC driving its datain port Info (169070): Pin DRAM_DQ[14] has VCC driving its datain port Info (169070): Pin DRAM_DQ[15] has VCC driving its datain port Info (169070): Pin FPGA_I2C_SDAT has VCC driving its datain port Info (169070): Pin PS2_CLK has VCC driving its datain port Info (169070): Pin PS2_CLK2 has VCC driving its datain port Info (169070): Pin PS2_DAT has VCC driving its datain port Info (169070): Pin PS2_DAT2 has VCC driving its datain port Info (169070): Pin HPS_CONV_USB_N has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[8] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[9] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[10] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[11] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[12] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[13] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[14] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[15] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[16] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[17] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[18] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[19] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[20] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[21] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[22] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[23] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[24] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[25] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[26] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[27] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[28] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[29] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[30] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQ[31] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQS_N[1] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQS_N[2] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQS_N[3] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQS_P[1] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQS_P[2] has VCC driving its datain port Info (169070): Pin HPS_DDR3_DQS_P[3] has VCC driving its datain port Info (169070): Pin HPS_ENET_INT_N has VCC driving its datain port Info (169070): Pin HPS_ENET_MDIO has VCC driving its datain port Info (169070): Pin HPS_FLASH_DATA[0] has VCC driving its datain port Info (169070): Pin HPS_FLASH_DATA[1] has VCC driving its datain port Info (169070): Pin HPS_FLASH_DATA[2] has VCC driving its datain port Info (169070): Pin HPS_FLASH_DATA[3] has VCC driving its datain port Info (169070): Pin HPS_GPIO[0] has VCC driving its datain port Info (169070): Pin HPS_GPIO[1] has VCC driving its datain port Info (169070): Pin HPS_GSENSOR_INT has VCC driving its datain port Info (169070): Pin HPS_I2C1_SCLK has VCC driving its datain port Info (169070): Pin HPS_I2C1_SDAT has VCC driving its datain port Info (169070): Pin HPS_I2C2_SCLK has VCC driving its datain port Info (169070): Pin HPS_I2C2_SDAT has VCC driving its datain port Info (169070): Pin HPS_I2C_CONTROL has VCC driving its datain port Info (169070): Pin HPS_KEY has VCC driving its datain port Info (169070): Pin HPS_LED has VCC driving its datain port Info (169070): Pin HPS_SD_CMD has VCC driving its datain port Info (169070): Pin HPS_SD_DATA[0] has VCC driving its datain port Info (169070): Pin HPS_SD_DATA[1] has VCC driving its datain port Info (169070): Pin HPS_SD_DATA[2] has VCC driving its datain port Info (169070): Pin HPS_SD_DATA[3] has VCC driving its datain port Info (169070): Pin HPS_SPIM_SS has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[0] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[1] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[2] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[3] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[4] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[5] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[6] has VCC driving its datain port Info (169070): Pin HPS_USB_DATA[7] has VCC driving its datain port Info (169186): Following groups of pins have the same dynamic on-chip termination control Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|diff_dtc_bar Info (169066): Type bi-directional pin HPS_DDR3_DQS_N[0] uses the Differential 1.5-V SSTL Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[0] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[1] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[2] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[3] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[4] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[5] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[6] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|delayed_oct Info (169066): Type bi-directional pin HPS_DDR3_DQ[7] uses the SSTL-15 Class I I/O standard Info (169185): Following pins have the same dynamic on-chip termination control: unnamed:u0|unnamed_hps_0:hps_0|unnamed_hps_0_hps_0:hps_0|unnamed_hps_0_hps_0_hps_io:hps_io|unnamed_hps_0_hps_0_hps_io_border:border|hps_sdram:hps_sdram_inst|hps_sdram_p0:p0|hps_sdram_p0_acv_hard_memphy:umemphy|hps_sdram_p0_acv_hard_io_pads:uio_pads|hps_sdram_p0_altdqdqs:dq_ddio[0].ubidir_dq_dqs|altdq_dqs2_acv_connect_to_hard_phy_cyclonev:altdq_dqs2_inst|diff_dtc Info (169066): Type bi-directional pin HPS_DDR3_DQS_P[0] uses the Differential 1.5-V SSTL Class I I/O standard Error (11802): Can't fit design in device. Modify your design to reduce resources, or choose a larger device. The Intel FPGA Knowledge Database contains many articles with specific details on how to resolve this error. Visit the Knowledge Database at https://www.altera.com/support/support-resources/knowledge-base/search.html and search for this specific error message number. Error: Quartus Prime Fitter was unsuccessful. 7 errors, 5 warnings Error: Peak virtual memory: 5113 megabytes Error: Processing ended: Sun Mar 22 17:55:31 2026 Error: Elapsed time: 00:00:06 Error: Total CPU time (on all processors): 00:00:05 Error (293001): Quartus Prime Full Compilation was unsuccessful. 9 errors, 341 warnings |
로직이 부족한줄 알았는데 핀이 너무 많이 할당되어도 그런 에러가 발생하는 건가?
[링크 : https://stackoverflow.com/questions/50442061/quartus-unable-to-fit-design-to-device]
| nios II 단종 (0) | 2026.03.22 |
|---|---|
| fpga sdk for openCL (0) | 2026.03.18 |
| aocl_c5soc_getting_started.pdf (Altera SDK for OpenCL) (0) | 2026.03.18 |
| de1-soc와 quartus / fpga sdk for opencl (0) | 2026.03.18 |
| quartus prime standard 실행 (0) | 2026.03.17 |
회사에서는 멀티 충전기로 했어서 그런가 wifi 꽂고나서는 안켜지던데
집에서 5V 2A 짜리 단독으로 물리니 문제없이 작동한다.
인터넷 찾아봐도 소비전력 이야기가 딱히 없던데(몇 mW 라던가..) 그냥 그러려니 하고 써야하나?
| $ ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:58:b4:8a:df txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:04:4b:e5:59:5d txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 150 base 0xc000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 112 bytes 9000 (9.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 112 bytes 9000 (9.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether aa:be:7b:09:f3:5d txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether aa:be:7b:09:f3:5f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 74:d8:3e:44:9f:17 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
| $ lspci -t -v -[0000:00]-+-01.0-[01]----00.0 Intel Corporation Wireless 8265 / 8275 \-02.0-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller $ lspci 00:01.0 PCI bridge: NVIDIA Corporation Device 0fae (rev a1) 00:02.0 PCI bridge: NVIDIA Corporation Device 0faf (rev a1) 01:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) $ lspci -v 00:01.0 PCI bridge: NVIDIA Corporation Device 0fae (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 84 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: 13000000-130fffff Capabilities: </access denied> Kernel driver in use: pcieport 00:02.0 PCI bridge: NVIDIA Corporation Device 0faf (rev a1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 84 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00001000-00001fff Memory behind bridge: 13100000-131fffff Capabilities: </access denied> Kernel driver in use: pcieport 01:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) Subsystem: Intel Corporation Dual Band Wireless-AC 8265 Flags: bus master, fast devsel, latency 0, IRQ 408 Memory at 13000000 (64-bit, non-prefetchable) [size=8K] Capabilities: </access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 406 I/O ports at 1000 [size=256] Memory at 13104000 (64-bit, non-prefetchable) [size=4K] Memory at 13100000 (64-bit, non-prefetchable) [size=16K] Capabilities: </access denied> Kernel driver in use: r8168 |
mini-pciex도 아니고 왜 m.2로 만드는진 모르겠지만
아무튼 m.2 폼팩터의 무선랜이고
i-pex의 MHF4 (혹은 ipex4라고 표기) 커넥터의 듀얼 안테나 제품이다.
랜카드가 7천원 + 3천인데
[링크 : https://itempage3.auction.co.kr/DetailView.aspx?itemno=F310755633]
MHF4가 2800원 + 3천원. 배보다 배꼽이 더 큰 느낌이고
그 와중에 저건 또 케이블이라 SMA 2.4GHz 안테나가 필요하다는 것 이 또 추가지출을 하게 하네..
(회사에서 뽀려야지 -_-)
[링크 : https://itempage3.auction.co.kr/DetailView.aspx?itemno=E598839737]
| jetracer jetcard (0) | 2026.03.20 |
|---|---|
| seeed studio J202 carrier (0) | 2026.03.19 |
| jetson nano developer kit 4GB on! (0) | 2026.03.18 |
| jetracer + jetson nano dev. kit (4GB) (0) | 2026.03.18 |
| jetson nano developer kit 종류 조사 (0) | 2026.03.18 |
버전 차이가 있긴 한데
jetcard가 용량이 제법늘어나 있다.
보드리비전만 따지고 모듈 리비전은 안따지나?
[링크 : https://github.com/NVIDIA-AI-IOT/jetcard]
[링크 : https://m.blog.naver.com/zeta0807/221934764603]
[링크 : https://m.blog.naver.com/zeta0807/222043543005]
+
2026.03.21
jetcard로 굽고나서 부팅하니 먼가 뜨는데 안된다.
그래서 하라는대로 하려는데 이 미묘한(?) 함정은 멀까 ㅋㅋ
메모리 부족하니 이런거 설정해라 라고 하는데 실제로는 퍼미션에러 ㅋㅋㅋ
| $ jupyter lab build /usr/lib/python3/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) [LabBuildApp] JupyterLab 2.2.6 [LabBuildApp] Building in /usr/local/share/jupyter/lab [LabBuildApp] Building jupyterlab assets (build:dev:minimize) Build failed. Troubleshooting: If the build failed due to an out-of-memory error, you may be able to fix it by disabling the `dev_build` and/or `minimize` options. If you are building via the `jupyter lab build` command, you can disable these options like so: jupyter lab build --dev-build=False --minimize=False You can also disable these options for all JupyterLab builds by adding these lines to a Jupyter config file named `jupyter_config.py`: c.LabBuildApp.minimize = False c.LabBuildApp.dev_build = False If you don't already have a `jupyter_config.py` file, you can create one by adding a blank file of that name to any of the Jupyter config directories. The config directories can be listed by running: jupyter --paths Explanation: - `dev-build`: This option controls whether a `dev` or a more streamlined `production` build is used. This option will default to `False` (ie the `production` build) for most users. However, if you have any labextensions installed from local files, this option will instead default to `True`. Explicitly setting `dev-build` to `False` will ensure that the `production` build is used in all circumstances. - `minimize`: This option controls whether your JS bundle is minified during the Webpack build, which helps to improve JupyterLab's overall performance. However, the minifier plugin used by Webpack is very memory intensive, so turning it off may help the build finish successfully in low-memory environments. An error occured. PermissionError: [Errno 13] Permission denied: '/usr/local/share/jupyter/lab/staging/index.js' See the log file for details: /tmp/jupyterlab-debug-nd1103ww.log |
기본 패스워드는 jetson이다.
아무튼 잘 빌드된다. 역시 4GB!
| $ sudo jupyter lab build [sudo] password for jetson: /usr/lib/python3/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) [LabBuildApp] JupyterLab 2.2.6 [LabBuildApp] Building in /usr/local/share/jupyter/lab [LabBuildApp] Building jupyterlab assets (build:dev:minimize) |
메모리 더 확보하려고 X 죽이려고 하는데 안네.. (gdm, gdm3 stop으로는 안됨)
역시 single user로 해야하나..
| $ free -h total used free shared buff/cache available Mem: 3.9G 630M 2.7G 28M 545M 3.1G Swap: 5.9G 0B 5.9G |
아까는 disable 안하고 stop만 해서 그런가?
아무튼 약 140MB 더 확보가 가능하다.
| $ sudo systemctl disable gdm3 [sudo] password for jetson: Synchronizing state of gdm3.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install disable gdm3 $ free -h total used free shared buff/cache available Mem: 3.9G 619M 2.7G 28M 546M 3.1G Swap: 5.9G 0B 5.9G $ sudo systemctl stop gdm3 $ free -h total used free shared buff/cache available Mem: 3.9G 475M 2.9G 27M 545M 3.3G Swap: 5.9G 0B 5.9G |
주피터 접속하니 475MB 에서 순간 769MB 까지 증가하더니 595MB로 줄어든다.
2기가 에서는 gdm 꺼도 스왑쓰지 않으면 위험할지도?
| $ free -h total used free shared buff/cache available Mem: 3.9G 475M 2.9G 27M 545M 3.3G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 517M 2.8G 27M 555M 3.3G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 570M 2.8G 27M 559M 3.2G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 525M 2.8G 27M 561M 3.3G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 543M 2.8G 27M 562M 3.3G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 614M 2.7G 27M 563M 3.2G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 666M 2.7G 27M 563M 3.1G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 722M 2.6G 27M 564M 3.1G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 747M 2.6G 27M 564M 3.1G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 769M 2.6G 27M 567M 3.0G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 602M 2.7G 27M 567M 3.2G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 607M 2.7G 27M 567M 3.2G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 607M 2.7G 27M 567M 3.2G Swap: 5.9G 0B 5.9G $ free -h total used free shared buff/cache available Mem: 3.9G 595M 2.7G 27M 567M 3.2G Swap: 5.9G 0B 5.9G |
[링크 : https://eteo.tistory.com/997]
[링크 : https://forums.developer.nvidia.com/t/disabling-the-desktop-gui/257951]
| jetson nano + m.2 wifi (0) | 2026.03.20 |
|---|---|
| seeed studio J202 carrier (0) | 2026.03.19 |
| jetson nano developer kit 4GB on! (0) | 2026.03.18 |
| jetracer + jetson nano dev. kit (4GB) (0) | 2026.03.18 |
| jetson nano developer kit 종류 조사 (0) | 2026.03.18 |
화면에서는 Next 이런게 나오는데 소스에는 없어서 열어보니 QWizard 라는 클래스를 사용중이라 조사.
setTitle로 상단에 표시되는 항목이 지정되고
실제 내용이 label 을 통해 별도로 추가된다.
| QWizardPage *createIntroPage() { QWizardPage *page = new QWizardPage; page->setTitle("Introduction"); QLabel *label = new QLabel("This wizard will help you register your copy " "of Super Product Two."); label->setWordWrap(true); QVBoxLayout *layout = new QVBoxLayout; layout->addWidget(label); page->setLayout(layout); return page; } |
위저드를 써서 그런가 엄청 심플해진다.
| QWizard wizard; wizard.addPage(createIntroPage()); wizard.addPage(createRegistrationPage()); wizard.addPage(createConclusionPage()); //! [linearAddPage] wizard.setWindowTitle("Trivial Wizard"); wizard.show(); |
[링크 : https://doc.qt.io/qt-6/qtwidgets-dialogs-trivialwizard-example.html]
| qt qrc 리소스 등록 후 이미지로 띄우기 (0) | 2026.03.23 |
|---|---|
| qt 6 프로그래밍 공개 ebook (0) | 2026.03.23 |
| qt widget 화면 전환 (0) | 2026.03.18 |
| qt qml 와 c++ 상호연동 (0) | 2026.01.16 |
| qt quick websocket (0) | 2026.01.14 |
|
