에뮬레이터 배포판(?)
[링크 : http://blog.petrockblock.com/retropie/]
[링크 : http://blog.petrockblock.com/retropie/retropie-downloads/]
| 지름신 강림! - 라즈베리 2b(본체만) (0) | 2016.03.10 |
|---|---|
| 라즈베리 3B? (0) | 2016.03.06 |
| openELEC 6.0.0 릴리즈 (0) | 2016.01.03 |
| 라즈베리 2b lirc + openELEC 설정 (0) | 2015.12.12 |
| 라즈베리 파이 zero...??? (0) | 2015.11.27 |
그래서.. TED 라던가..
각종 플러그 인들이 요 근래부터 설치가 안된걸려나?
Published: Sunday, 01 November 2015 23:21
The OpenELEC team is proud to announce OpenELEC 6.0 (6.0.0)
The most visible change is Kodi 15.2 (Isengard). Beginning with Kodi 15.0 most audio encoder, audio decoder, PVR and visualisation addons are no longer pre-bundled into OpenELEC but can be downloaded from the Kodi addon repo if required. PVR backends such as VDR and TVHeadend will install needed dependencies automatically. For further information on Kodi 15.1 please read http://kodi.tv/kodi-15-2-isengard-final-release/.
[링크 : http://openelec.tv/news/22-releases/172-release-openelec-6-0-released]
언어 추가 설치 부터 되는게 없네 -_-
수동으로 zip 파일 받아서 addon 설치 하듯 해야 한다 -_-
| 라즈베리 3B? (0) | 2016.03.06 |
|---|---|
| 레트로 파이(retropie) (0) | 2016.01.05 |
| 라즈베리 2b lirc + openELEC 설정 (0) | 2015.12.12 |
| 라즈베리 파이 zero...??? (0) | 2015.11.27 |
| 라즈베리 파이 Zero @ 5$ ?!?!? (2) | 2015.11.26 |
집에 있는 DS213j가 armv7 계열인데
문득 보다 보니 feature에 neon이 없는걸 발견
> cat /proc/cpuinfo
Processor : Marvell PJ4Bv7 Processor rev 1 (v7l)
BogoMIPS : 1196.85
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16 tls
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x581
CPU revision : 1
Hardware : Marvell Armada-370
Revision : 0000
Serial : 0000000000000000
검색을 해보니...
스펙 시트에도 vfp 언급은 있어도 neon은 없어서 다시 검색..
[링크 : http://www.marvell.com/embedded-processors/armada-370/]
엥? 375는 neon 첨가! 370은 없어영~ 라고?!?!
The Armada 375 resembles the Armada 370, which has one of Marvell’s ARMv7-compatible PJ4 cores running at 1.2GHz. Although this home-grown CPU is clocked 20% faster than the 375’s Cortex-A9 cores, it lacks Neon extensions and has a less capable version of the VFP unit.
[링크 : http://www.linleygroup.com/newsletters/newsletter_detail.php?num=5010]
| j-link segger j-flash (0) | 2016.09.02 |
|---|---|
| ulink flashmagic (0) | 2016.09.02 |
| jtag/swd pullup & pulldown (0) | 2015.12.17 |
| jtag과 swd (0) | 2015.12.14 |
| 비글본 github 저장소 (0) | 2015.10.30 |
lm3s1607 데이터 시트
TxFIFO가 있는데 이녀석에서 Transmitter로 한 바이트가 보내지면 TX 인터럽트가 떨어진다.
그런 이유로 가장 마지막 바이트가 UART를 통해 보내지는 시점에 (다음 바이트를 받기 위해) TX 인터럽트가 발생한다.
그래서 485 등을 사용시에는 TX 인터럽트 떨어졌다고 바로 TX Enable을 꺼버리면 안된다.
| cortex-m3 hibernate module... (0) | 2016.04.14 |
|---|---|
| cortex-m3 인터럽트 관련 조사 (0) | 2016.02.18 |
| coflash 구조 및 에러 메시지.. (0) | 2015.12.11 |
| ADCHardwareOversampleConfigure() (0) | 2015.11.17 |
| lm3s811 / lm31968 adc 사양비교 (0) | 2015.11.17 |
대충 보면 어셈인줄 알았는데.. 스크립트라네...
[링크 : http://wiki.osdev.org/Linker_Scripts]
[링크 : http://www.scoberlin.de/content/media/http/informatik/gcc_docs/ld_3.html]
[링크 : http://korea.gnu.org/manual/release/ld/ld-mahajjh/ld_3.html]
| PCB 마킹 의미 (0) | 2016.07.28 |
|---|---|
| COM26T2844VTX 관련... (0) | 2016.03.16 |
| 시리얼 저항 / 직렬 저항 / 댐핑 저항 (0) | 2015.12.17 |
| microchip PIC (0) | 2015.09.08 |
| 9$ computer C.H.I.P? (0) | 2015.05.27 |
이게 다 같은 건가?
일단 이걸 쓰는 이유는
1. 전류제한
2. 임피던스 매칭으로 노이즈 제거
3. 전압변경(좋은 방법은 아니지만)
등등등...
[링크 : http://programfrall.tistory.com/43]
[링크 : http://pcbee.tistory.com/entry/직렬series-저항-값에-대한-고찰]
[링크 : http://blog.naver.com/rlaghlfh/110127337569] 댐핑 저항
[링크 : http://www.solvline.com/technical_info/tech_note_view.php?no=24] 종단 저항(terminator)
| COM26T2844VTX 관련... (0) | 2016.03.16 |
|---|---|
| 링커 스크립트 문법(ld syntax) (0) | 2015.12.17 |
| microchip PIC (0) | 2015.09.08 |
| 9$ computer C.H.I.P? (0) | 2015.05.27 |
| PowerQUICC (0) | 2015.04.02 |
흐음...
pull up/down 저항이 낮아서 문제가 되려나?
[링크 : http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/348680/1220668]
[링크 : http://www.alteraforum.com/forum/archive/index.php/t-32059.html]
| JTAG Mode | SWD Mode | Signal | Required pull-up / pull-down (if not implemented internally by MCU) |
| TCK | SWCLK | Clock into the core | Use 10K-100K Ohm pull-down resistor to GND |
| TDI | - | JTAG Test Data Input | Use 10K-100K Ohm pull-up resistor to VCC |
| TDO | SWV | JTAG Test Data Output / SWV trace data output (SWO) | Use 10K-100K Ohm pull-up resistor to VCC |
| TMS | SWDIO | JTAG Test Mode Select / SWD data in/out | Use 10K-100K Ohm pull-up resistor to VCC |
| GND | GND | - | - |
[링크 : https://www.lpcware.com/content/faq/lpcxpresso/debug-design]
[링크 : http://www.support.code-red-tech.com/CodeRedWiki/HardwareDebugConnections] 조만간 폭파
| Signal | Connects to... |
|---|---|
| TMS | Test Mode State pin — Use 100K Ohm pull-up resistor to VCC. |
| TDO | Test Data Out pin. |
| RTCK | JTAG Return Test ClocK. (see Note below) |
| TDI | Test Data In pin — Use 100K Ohm pull-up resistor to VCC. |
| TRST | Test ReSeT/ pin — Use 100K Ohm pull-up resistor to VCC. TRST is optional and not available on some devices. You may leave it unconnected. |
| TCLK | Test CLocK pin — Use 100K Ohm pull-down resistor to GND. |
| VCC | Positive Supply Voltage — Power supply for JTAG interface drivers. |
| GND | Digital ground. |
| RESET | RSTIN/ pin — Connect this pin to the (active low) reset input of the target CPU. |
| CPUCLK | CPU clock (according IEEE Standard 1149.1). |
| OCDSE | Enable/Disable OCDS interface (Infineon-specific). |
| TRAP | Trap condition (Infineon-specific). |
| BRKIN | Hardware break in (Infineon-specific). |
| BRKOUT | Hardware break out (Infineon-specific). |
| /JEN | JTAG Enable (STMicroelectronics specific). |
| TSTAT | JTAG ISP Status (STMicroelectronics specific) (optional). |
| /RST | Chip reset (STMicroelectronics specific). |
| /TERR | JTAG ISP Error (STMicroelectronics specific) (optional). |
[링크 : http://www.keil.com/support/man/docs/ulink2/ulink2_hw_connectors.htm]
[링크 : http://forum.falinux.com/zbxe/?document_srl=796669...]
| ulink flashmagic (0) | 2016.09.02 |
|---|---|
| armada 370 - ARMv7 인데 neon이 없네? (0) | 2015.12.30 |
| jtag과 swd (0) | 2015.12.14 |
| 비글본 github 저장소 (0) | 2015.10.30 |
| arm9 dsp / arm11 simd instuction 비교? (0) | 2015.10.01 |
음.. 소스 레벨에서는 역시 무리이고..
돌려보고 최대로 먹는거 보면서 분할을 해줘야 하려나?
[링크 : http://www.freertos.org/FAQMem.html]
[링크 : http://www.microchip.com/forums/m590414.aspx]
[링크 : http://sourceforge.net/p/freertos/discussion/382005/thread/33791e60/]
[링크 : http://www.freertos.org/uxTaskGetStackHighWaterMark.html]
[링크 : http://www.freertos.org/Stacks-and-stack-overflow-checking.html]
| esp32 freertos (0) | 2023.12.08 |
|---|---|
| stm32 freertos (0) | 2023.12.08 |
| lm3s811 freeRTOS ADC... (0) | 2015.11.16 |
| freertos 자료 (0) | 2015.11.12 |
| freeRTOS 패키지? (0) | 2015.11.11 |
걍 포기할까...
LD_LIBRARY_PATH 잘못설정하면 절대 좋은꼴을 못보는데... ㄷㄷㄷ
./as: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
$ sudo apt-get install zlib1g:i386
$ sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
[링크 : http://stackoverflow.com/questions/21256866/libz-so-1-cannot-open-shared-object-file]
/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
export LD_LIBRARY_PATH="/usr/local/lib" sudo ldconfig
[링크 : http://stackoverflow.com/.../cc1-error-while-loading-shared-libraries-libmpc-so-2-...c]
$ sudo find / -name "libmpc.so.*"
/usr/lib/x86_64-linux-gnu/libmpc.so.2.0.0
/usr/lib/x86_64-linux-gnu/libmpc.so.2
$ sudo apt-cache search libmpc
libmpc-dev - multiple precision complex floating-point library development package
libmpc2 - multiple precision complex floating-point library
libmpcdec-dev - MusePack decoder - development files
libmpcdec6 - MusePack decoder - library
mppenc - Musepack lossy audio codec encoder
이거.. 볼수록 잘못 건드리면 헬게이트 열릴 기분인데?
as: error while loading shared libraries: libopcodes-2.23.51.20121129.so: cannot open shared object file: No such file or directory
| openRISC on FPGA (0) | 2018.01.29 |
|---|---|
| openRISC OR1k(1000) OR1200 (0) | 2015.12.11 |
| openrisc 어셈블리 (0) | 2015.12.10 |
| openRISC chaintool (0) | 2015.11.27 |
음.. JTAG없이 SWD만으로 하는데
SWD로 안되면.. 머가 문제일려나..
TCK/TMS 인식인가..?
How do I switch the debugger connection between JTAG and SWD (Serial Wire Debug) protocol?
Applies to: Debug Access Port (DAP)
Answer
The SWJ-DP component supports both protocols - Serial Wire and JTAG. The selector is part of the SWJ-DP.
The default protocol at power-up is JTAG, so if you want to use Serial Wire, you need to use the TCK and TMS pins to scan in a special 'key', which is a sequence of TMS values which has no effect for a pure JTAG TAP but is recognized by a SWJ-DP TAP as a request to switch into Serial Wire mode. Similarly, there is another another TMS sequence to switch back from SWD to JTAG protocol.
[링크 : http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka11775.html]
| armada 370 - ARMv7 인데 neon이 없네? (0) | 2015.12.30 |
|---|---|
| jtag/swd pullup & pulldown (0) | 2015.12.17 |
| 비글본 github 저장소 (0) | 2015.10.30 |
| arm9 dsp / arm11 simd instuction 비교? (0) | 2015.10.01 |
| arm11 simd instruction (0) | 2015.10.01 |
|
