비싼 zynq를 두고 PS 안쓰고 PL만 쓸 수 있냐라는 고민을 하는게 웃기긴 한데
느낌이. FSBL(first stage boot loader)는 PS에서 구동하고, PL 비트스트림 읽어 들인후 PS를 쓰지 않은 뿐인 느낌?
| zynq 7000 fsbl (0) | 2023.07.12 |
|---|---|
| zynq fsbl (0) | 2023.07.07 |
| xilinx uartlite on zynq (0) | 2023.05.16 |
| xilinx vivado uart ip (0) | 2023.05.12 |
| xilinx bram uram (0) | 2023.05.12 |
신기하게도 칩에 HDMI 2.0 RX 인터페이스가 존재한다.
| :/ # v4l2-ctl -d /dev/video8 -V -D Driver Info: Driver name : rk_hdmirx Card type : rk_hdmirx Bus info : fdee0000.hdmirx-controller Driver version : 5.10.66 Capabilities : 0x84201000 Video Capture Multiplanar Streaming Extended Pix Format Device Capabilities Device Caps : 0x04201000 Video Capture Multiplanar Streaming Extended Pix Format |
[링크 : https://wiki.t-firefly.com/en/Core-3588J/usage_hdmiin.html]
| HDMI RX interface Support HDMI RX 2.0, up to 4K@60fps video input Support HDCP2.3 |
[링크 : https://www.cnx-software.com/pdf/Rockchip%C2%A0RK3588%C2%A0Datasheet%C2%A0V0.1-20210727.pdf]
| orange pi 3 못써먹겠네! (0) | 2023.07.07 |
|---|---|
| orange pi 3 install_to_emmc 는 실패, dd는 성공 (0) | 2023.07.06 |
| android on orange pi 3 (0) | 2022.12.07 |
| allwinner A시리즈 백도어 (0) | 2022.11.06 |
| orange pi 3 관련 문서 (0) | 2022.01.03 |
다시 문서를 보니 이전에 10.1 단계를 건너뛰고 10.2만 진행한 것 같다.
아무생각 없이 무지성으로 win 10 x64용 에서 해당 파일 꺼내려고 보니 2GB.
아키텍쳐가 안되겠지...? 라는 생각에
win 10 iot ent 다운로드 받는데 4시간..(32bit / 64bit + 영어 / 국문...)
| 10.1 Flashing Windows 10 IoT Installer to the SD card Currently, the only way to deploy a Windows IoT Enterprise on the onboard eMMC is to use WinPE. OS (Windows Preinstallation Environment) to write the Windows IoT image to eMMC. Windows manufacturing OS (WinPE) that can be fully loaded and run from memory without using persistent storage. The following steps create an SD card with WinPE and a Windows IoT image that contains the BSP drivers. The boot firmware checks the SD card and boots WinPE, which then installs the Windows IoT image to the eMMC. 1. Decompress the W21H2-1-x-x-imx-windows-bsp-binaries.zip file. The package contains release-signed prebuilt binaries and image files. 2. Open the elevated command prompt and navigate to the IoTEntOnNXP directory. 3. Mount the previously downloaded Windows IoT Enterprise ISO image file (see chapter Software requirements) and copy the install.wim file from the <DVD mount drive:>\sources\install.wim to the IoTEntOnNXP directory. 4. Execute the command: make-winpe-enterprise.cmd /disable_updates /disable_transparency /test_signing This command creates a copy of the selected install.wim image with injected i.MX drivers and applied updates from the kbpatch/ directory. These patches are for Windows 21H2, build 19044.1288 and update the image to build 19044.2566. Note: Be sure to copy the whole command line. 5. Execute the command: make-winpe-enterprise.cmd /apply <disk_number> where <disk_number> is the physical number of the SD card disk on your PC. It can be obtained using the Disk Management tool (right-click the start menu icon and select Disk Management). This command deploys the WinPE image to the SD card. CAUTION: Make sure to select the correct disk number, as this step formats the selected disk! The WinPEbased Windows installer is now deployed on the SD card. 6. Continue with the firmware installation to the SD card. 10.2 Flashing firmware to the SD card During active development of the boot firmware, it can be time-consuming and error-prone to repeatedly change the dip switches between UUU download mode and eMMC boot mode. To simplify this process, the i.MX EVK boards support SD card boot mode that allows you to keep the boot firmware on an SD card. To deploy boot firmware to an SD card from Windows, we recommend using the Cfimager tool from https://www. nxp.com/webapp/Download?colCode=CF_IMAGER. Perform the following steps to flash the firmware to the SD card: 1. Download the NXP cfimager tool and copy it into the firmware directory or a directory listed in the system environment variable %PATH%. 2. Navigate to the firmware directory. 3. Plug the SD card into the host PC and execute the following board-specific command: For i.MX 8M Mini EVK board: flash_bootloader.cmd /device MX8M_MINI_EVK /target_drive <SD card driver letter, for example, f:> For i.MX 8M Quad EVK board: flash_bootloader.cmd /device MX8M_EVK /target_drive <SD card driver letter, for example, f:> For i.MX 8M Nano EVK board: flash_bootloader.cmd /device MX8M_NANO_EVK /target_drive <SD card driver letter, for example, f:> For i.MX 8M Plus EVK board: flash_bootloader.cmd /device MX8M_PLUS_EVK /target_drive <SD card driver letter, for example, f:> For i.MX 8QuadXPlus MEK board: flash_bootloader.cmd /device MX8QXP_MEK /target_drive <SD card driver letter, for example, f:> For i.MX 93 EVK board: flash_bootloader.cmd /device MX93_11X11_EVK /target_drive <SD card driver letter, for example, f:> 4. Power off the board. 5. Insert the SD card to the board. 6. Change the boot device to the SD card. 7. Power on the board |
[링크 : https://www.nxp.com/docs/en/quick-reference-guide/IMXWQSG.pdf]
+
다시 시도 하는데 이런저런 또 막히는 것들 산더미 -_-
| C:\nxp\W21H2-1-3-0-imx-windows-bsp-binaries\IoTEntOnNXP>make-winpe-enterprise.cmd /disable_updates /disable_transparency /test_signing You must install the Windows PE Add-on for the ADK https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/download-winpe--windows-pe Script failed Cleaning up 배포 이미지 서비스 및 관리 도구 버전: 10.0.22621.1 오류: 50 지원되지 않는 요청입니다. DISM 로그 파일은 C:\Windows\Logs\DISM\dism.log에 있습니다. 배포 이미지 서비스 및 관리 도구 버전: 10.0.22621.1 오류: 50 지원되지 않는 요청입니다. DISM 로그 파일은 C:\Windows\Logs\DISM\dism.log에 있습니다. C:\nxp\W21H2-1-3-0-imx-windows-bsp-binaries\IoTEntOnNXP\diskpart.txt을(를) 찾을 수 없습니다. |
그래서 PE Addon 만 까는 청개구리 짓을 발동!
다시 문서를 읽어 보니 adk for win10, winpe addon for adk 2004 두개를 깔아야 한다고 한데 winPE add-on for ADK 만 설치해도 일단은 넘어간다.
| 3 Software requirements • Binary drivers and firmware (either downloaded from nxp.com or built locally) • Windows IoT operating system. There are two options: – Visual Studio Subscription portal my.visualstudio.com – At the portal, click Downloads -> Windows 10 -> Search for “Windows 10 IoT Enterprise LTSC 2021” or “Windows 10 IoT Enterprise 2021” – The default architecture is set to x64, click the dropdown menu to change it to Arm64 and download the DVD – Through microsoftoem.com facilitated by a Windows IoT OS distributor – To find a distributor, visit aka.ms/iotdistributorlist • Windows ADK for Windows 10 and Windows PE add-on for ADK, version 2004. |
다시 시도하니 되는것 같긴한데
무지성으로(!) 받은 x86 , x64용 Win IoT Ent 라서 ARM64 아니라고 뱉는다.
| C:\nxp\W21H2-1-3-0-imx-windows-bsp-binaries\IoTEntOnNXP>make-winpe-enterprise.cmd /disable_updates /disable_transparency /test_signing Selected: "install.wim" Source image: install.wim Test signing: yes Patch Sdport: no Windows debug over ethernet: no, IP: Windows PE debug over ethernet: no, IP: KD_NET file (for debug over net): no Windows debug over serial: no Windows PE debug over serial: no Unattended install answer file: no Disable updates: yes Disable transparency: yes Split wim: no Cummulative update: no, path: ********************************************************************************************************************************************************* +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ *** Step 1 Creating i.MX Windows IoT Enterprise image: out\imx_win_iot_install.wim ********************************************************************************************************************************************************* +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Cleaning up from previous run --------------------------------------------------------------------------------------------------------------------------------------------------------- *** Step 1.1 Copying Windows Enterprise image install.wim to out\imx_win_iot_install.wim --------------------------------------------------------------------------------------------------------------------------------------------------------- 하위 디렉터리 또는 파일 out이(가) 이미 있습니다. copy "install.wim" "out\imx_win_iot_install.wim" 1개 파일이 복사되었습니다. --------------------------------------------------------------------------------------------------------------------------------------------------------- *** Step 1.2 Mounting i.MX Windows IoT Enterprise image at out\mount_enterprise --------------------------------------------------------------------------------------------------------------------------------------------------------- dism /mount-wim /wimfile:"out\imx_win_iot_install.wim" /mountdir:"out\mount_enterprise" /index:2 배포 이미지 서비스 및 관리 도구 버전: 10.0.22621.1 오류: 0xc1510113 지정한 이미지가 WIM에 없습니다. WIM에서 먼저 기존 이미지가 있는지 확인하십시오. DISM 로그 파일은 C:\Windows\Logs\DISM\dism.log에 있습니다. |
| NXP i.mx8mp LF_v6.1.55-2.2.0 테스트 (0) | 2023.12.21 |
|---|---|
| missed: not vectorized: relevant stmt not supported: (0) | 2023.08.31 |
| nxp i.mx8mp win iot (0) | 2023.05.26 |
| rpmsg-lite (0) | 2023.03.23 |
| i.mx8m plus cortex-m7 part.2 (0) | 2023.02.23 |
baudrate 보소.. 이런 변태 같은 -_-
| 3.1 Serial logging setup To help troubleshoot issues during boot, use the USB micro-B port on i.MX EVK boards to output U-Boot and UEFI firmware serial debug logs to a host PC. The USB micro-B port on the EVK presents a virtual serial port to the host PC, which can be read by common Windows serial terminal applications such as HyperTerminal, Tera Term, or PuTTY. 1. Connect the target and the PC using the cable mentioned above. 2. Open Device Manager on the PC and locate the Enhanced Virtual serial device and note the COM port number. 3. Open the terminal on the PC. Configure the Enhanced Virtual serial/COM port to 921600 baud/s, 8-bit, onestop bit. |
[링크 : https://www.nxp.com/docs/en/quick-reference-guide/IMXWQSG.pdf]
아무튼 baudrate 맞추니 이상하게 라도 나온다(키보드 인식 안해서 uart를 통해서 제어해야 하다니 -_ㅠ)
Device manager 뜨는게 없다.
Boot Manager 에서는 UEFI 옵션별로 뜨는데
요건 i.mx8mp 보드의 eMMC로 부팅하는거. 어떤 버전이 구워져있는진 모르겠지만
부팅하다가 kernel panic 뜨는데 어쩌면 윈도우용으로 부트로더가 설정하는 바람에
uboot + kernel 에서 설정되지 않는 부분때문에 그런걸지도 모르겠다.
윈도우 IoT 이미지가 2.5MB 밖에 안되서 그런가 SD 카드로 부팅하려고 하면 진행이 안된다.
Boot Maintenance Manager 에서는 먼가 조금 뜨는데 들어간다고 먼가 되는게 있는 것도 아니라서..
그나마 console option 으로 들어가면 input / output / stderr 요런걸로 어떤 장치를 쓸거냐 정도만 나온다.
그냥 윈도우 처럼 GUI 화면은 도대체 어떻게 해야 하냐..
| missed: not vectorized: relevant stmt not supported: (0) | 2023.08.31 |
|---|---|
| nxp i.mx8mp win iot part 2 (0) | 2023.05.26 |
| rpmsg-lite (0) | 2023.03.23 |
| i.mx8m plus cortex-m7 part.2 (0) | 2023.02.23 |
| i.mx8m plus cortex-m7 (0) | 2023.02.23 |
커널에서 xilinx uartlite 쓰도록 해주고
device tree에서 axi 주소 추가해주고
vivado block design에서 axi와 PS로 uartlite 블록을 연결해주면 되는건가?
[링크 : https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842249/Uartlite+Driver]
| zynq fsbl (0) | 2023.07.07 |
|---|---|
| zynq w/o ps (0) | 2023.06.30 |
| xilinx vivado uart ip (0) | 2023.05.12 |
| xilinx bram uram (0) | 2023.05.12 |
| xilinx - partial bitstream (0) | 2023.04.24 |
cyclone IV 에서는 M9K 인것 같고
cyclone V 에서는 M10K 인가?
de10-nano 다운로드 받아서 IP catalog에서 해보니 아래와 같이 나온다.
| M9K and M10K memories are Intel/Altera’s embedded highdensity memory arrays – Nearly all modern FPGAs include similar “block memories” • Each block contains approximately 9000 or 10,000 bits of memory per block respectively |
[링크 : https://www.ece.ucdavis.edu/~bbaas/181/notes/Handout.M9K.M10K.mems.pdf]
| terasic sockit (0) | 2023.11.06 |
|---|---|
| HSMC(High Speed Mezzanine Card) (0) | 2023.10.02 |
| altera uart ip (0) | 2023.05.14 |
| altera - partial reconfigure (0) | 2023.04.24 |
| altera nios 2 epcs to ram (0) | 2023.03.28 |
xilinx 에서 보다 intel fpga쪽 보니
라이센스 이야기도 없고(그냥 있으면 기본 무료라고 보면 되는건가..?) 웬지 불안해지는 느낌
얘가 HDL 레벨에서 설정해서 쓰는 간단한 uart ip고
16550 이 전체 사양 지원하는 uart 디바이스
cyclone iv 에서는 사용불가능한데
이름만 보면 xlinix의 uartlite 같지만, 전혀 다른 ip 같은 느낌이네..
그 와중에 시리얼 라이트라는데 내가 아는 그 시리얼이 아닌가?
| HSMC(High Speed Mezzanine Card) (0) | 2023.10.02 |
|---|---|
| altera(intel fpga) m9k m10k (0) | 2023.05.14 |
| altera - partial reconfigure (0) | 2023.04.24 |
| altera nios 2 epcs to ram (0) | 2023.03.28 |
| Nios V (0) | 2021.11.01 |
uart로 검색하니 uart 16550과 uartlite라는 녀석이 나온다.
둘 다 라이센스가 included 인데.. free도 있고 무슨 차이이려나?
uartlite는 baudrate와 parity를 HDL 로 설정해야 하고(런타임 변경 불가)
[링크 : https://www.xilinx.com/products/intellectual-property/axi_uartlite.html]
uart 16550은 런타임에 변경이 가능한 ip이다.
보기에는 freeze 하나만 더 추가되는 느낌이긴한데.. S_AXI 쪽이 많이 차이나려나?
[링크 : https://www.xilinx.com/products/intellectual-property/axi_uart16550.html]
| zynq w/o ps (0) | 2023.06.30 |
|---|---|
| xilinx uartlite on zynq (0) | 2023.05.16 |
| xilinx bram uram (0) | 2023.05.12 |
| xilinx - partial bitstream (0) | 2023.04.24 |
| vivado 설치 하려고 했더니. (0) | 2023.01.08 |
BRAM(Block RAM)
URAM(Ultra RAM) - ultraScale+ 이상 제품군용
[링크 : https://wikidocs.net/86996]
block memory generator 라는 IP를 이용해서 BRAM을 할당하도록 하여 사용
(즉, HDL 레벨에서 특정 BRAM을 쓰도록 할 순 없는 것으로 예상)
| xilinx uartlite on zynq (0) | 2023.05.16 |
|---|---|
| xilinx vivado uart ip (0) | 2023.05.12 |
| xilinx - partial bitstream (0) | 2023.04.24 |
| vivado 설치 하려고 했더니. (0) | 2023.01.08 |
| 흐음.. 끌리네? (0) | 2022.11.02 |
Arria 10 HPS에서만 되는진 찾아봐야 할 듯.
| Partial reconfiguration (PR) allows you to reconfigure a portion of the FPGA dynamically, while the remaining FPGA design continues to function |
[링크 : https://cdrdv2-public.intel.com/667007/an798-683034-667007.pdf]
어째 느낌이 HPS 라인업만 되는 것 같네?
| The Intel® Quartus® Prime software supports the PR feature for the Intel® Stratix® V device family and Cyclone® V devices whose part number ends in "SC", for example, 5CGXFC9E6F35I8NSC. |
| altera(intel fpga) m9k m10k (0) | 2023.05.14 |
|---|---|
| altera uart ip (0) | 2023.05.14 |
| altera nios 2 epcs to ram (0) | 2023.03.28 |
| Nios V (0) | 2021.11.01 |
| IOFS - Intel Open FPGA Stack (0) | 2021.07.06 |
|
