구차니의 잡동사니 모음

UHS-1 U3 sd 카드는 처음 만져보는데 (64GB) 30~50MB/s 사이에 뜨는 것 같다.

꾸준히 유지되는건 아니지만 순간적으로 60MB/s 까지도 올라온다.

배경화면 바꿔주는 유틸리티

윈도우10에서 쓰고 있는데 나쁘진 않아서 혹시 우분투용으로?! 해서 검색하니 나오긴 한다.

MS 공식 프로그램은 아닌듯

[링크 : https://snapcraft.io/bing-wall]

윈도우에서 한번 밀어 보려다가 드라이브가 M 막 이런게 떠서 놀람.

실제로 1~14까지 파티션이 존재하네?

[링크 : https://forums.developer.nvidia.com/t/jetson-nano-sd-card-partitions-can-not-extend/73032]

System throttled due to Over-current.

라는 말이 나와서 찾아보니 실제로 over current가 아니라 low voltage 경고라고..

[링크 : https://forums.developer.nvidia.com/t/system-throttled-due-to-over-current/158055/14]

일단은 외부배터리랑 몇개의 부품을 달아주면 쓸 수 는 있는 듯.

[링크 : https://forums.developer.nvidia.com/t/jetson-nano-development-board-and-rtc/160445]

[링크 : https://www.forecr.io/blogs/bsp-development/rtc-test-for-nvidia-jetson-modules]

[링크 : https://developer.ridgerun.com/wiki/index.php?title=Jetson_Nano/Introduction/Developer_Kit]

[링크 : https://custom-build-robots.com/top-story-en/nvidia-jetson-nano-real-time-clock-rtc-part-1/12774?lang=en]

[링크 : https://custom-build-robots.com/top-story-en/nvidia-jetson-nano-real-time-clock-rtc-part-2/12776?lang=en]

흐음.. 어떻게 가지고 놀지...

찾다보니 jetson nano developer kit과 2gb dev. kit 이 있어서 찾아보니

jetson nano 자체는 원래 4GB인데 메모리 반토막 내고

그 외에는 캐리어 보드에서 cost down 시킨 듯(dp, usb 3.0, csi 1개 채널 등)

[링크 : https://developer.nvidia.com/embedded/jetson-nano-2gb-developer-kit]

[링크 : https://developer.nvidia.com/embedded/jetson-nano-developer-kit]

2GB는 59$, 4GB는 99$.

가격 하락 폭을 보니 2GB 모델이 나쁘진 않는 느낌이네.

[링크 : https://developer.nvidia.com/embedded/faq]

eMMC 삭제

[링크 : https://developer.nvidia.com/embedded/jetson-modules]

+

그래서 이미지 다운로드도 경로가 다르다.

[링크 : https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-devkit#write]

[링크 : https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-2gb-devkit#write]

  [링크 : https://developer.nvidia.com/embedded/jetpack]

Getting Started with Jetson Nano 2GB Developer Kit

[링크 : https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-2gb-devkit]

핀헤더 정보

[링크 : https://developer.nvidia.com/embedded/learn/jetson-nano-2gb-devkit-user-guide#id-.JetsonNano2GBDeveloperKitUserGuidevbatuu_v1.0-40-PinHeader(J6)]

[링크 : https://developer.nvidia.com/embedded/learn/jetson-nano-2gb-devkit-user-guide]

2280 22mm * 80mm 규격

2242 (40이 아니었군)

와우.. 조합이 대환장이네 ㅋㅋㅋ

[링크 : https://en.wikipedia.org/wiki/M.2]

A1369

맥 에어 2011 mid / i5 1.7ghz / 13" 1440x900 / 1.35kg / nvme 제거 7만..

흐음. 아내님 윤허를 받아 일단 지르고

다음달에 nvme 질러서 한번 써볼까?

솔찍히 그냥 맥을 가지고, 써보고 싶다가 가장 큰거라 사서 머하는데 써먹지가 문제네?

[링크 : https://cafe.naver.com/joonggonara/892667172]

i5-2557m

[링크 : https://m.blog.naver.com/ingyw/120162250616]

[링크 : https://support.apple.com/kb/sp683?locale=ko_KR]

[링크 : https://ark.intel.com/.../intel-core-i5-2557m-processor-3m-cache-up-to-2-70-ghz.html]

nvme는 아니고 sata 타입.. 흐음..

[링크 : https://hoile.tistory.com/142]

option + 전원 on

[링크 : https://happycode.tistory.com/428] ssd 교치 시 os 설치방법

OS 버전은 high sierra 까지 가능하네

[링크 : https://support.apple.com/ko-kr/HT201862]

하나하나 조사하면서 지름신이 조금은 물리쳐지는 중 ㅠㅠ

상세 내용이 있으나 너무 길어서 눈에 안들어 오는데..

아무튼 요약하면 Direct는 일반 포인터, indirect는 링크드 리스크나 멀티 포인터 인데

이중할당해서 이전 할당을 추적하지 않을 경우라고 보면 될 듯.

     Pointer chain            AAA Leak Case   BBB Leak Case
     -------------            -------------   -------------
(1)  RRR ------------> BBB                    DR
(2)  RRR ---> AAA ---> BBB    DR              IR
(3)  RRR               BBB                    DL
(4)  RRR      AAA ---> BBB    DL              IL
(5)  RRR ------?-----> BBB                    (y)DR, (n)DL
(6)  RRR ---> AAA -?-> BBB    DR              (y)IR, (n)DL
(7)  RRR -?-> AAA ---> BBB    (y)DR, (n)DL    (y)IR, (n)IL
(8)  RRR -?-> AAA -?-> BBB    (y)DR, (n)DL    (y,y)IR, (n,y)IL, (_,n)DL
(9)  RRR      AAA -?-> BBB    DL              (y)IL, (n)DL

Pointer chain legend:
- RRR: a root set node or DR block
- AAA, BBB: heap blocks
- --->: a start-pointer
- -?->: an interior-pointer

Leak Case legend:
- DR: Directly reachable
- IR: Indirectly reachable
- DL: Directly lost
- IL: Indirectly lost
- (y)XY: it's XY if the interior-pointer is a real pointer
- (n)XY: it's XY if the interior-pointer is not a real pointer
- (_)XY: it's XY in either case
Every possible case can be reduced to one of the above nine. Memcheck merges some of these cases in its output, resulting in the following four leak kinds.

"Still reachable". This covers cases 1 and 2 (for the BBB blocks) above. A start-pointer or chain of start-pointers to the block is found. Since the block is still pointed at, the programmer could, at least in principle, have freed it before program exit. "Still reachable" blocks are very common and arguably not a problem. So, by default, Memcheck won't report such blocks individually.

"Definitely lost". This covers case 3 (for the BBB blocks) above. This means that no pointer to the block can be found. The block is classified as "lost", because the programmer could not possibly have freed it at program exit, since no pointer to it exists. This is likely a symptom of having lost the pointer at some earlier point in the program. Such cases should be fixed by the programmer.

"Indirectly lost". This covers cases 4 and 9 (for the BBB blocks) above. This means that the block is lost, not because there are no pointers to it, but rather because all the blocks that point to it are themselves lost. For example, if you have a binary tree and the root node is lost, all its children nodes will be indirectly lost. Because the problem will disappear if the definitely lost block that caused the indirect leak is fixed, Memcheck won't report such blocks individually by default.

"Possibly lost". This covers cases 5--8 (for the BBB blocks) above. This means that a chain of one or more pointers to the block has been found, but at least one of the pointers is an interior-pointer. This could just be a random value in memory that happens to point into a block, and so you shouldn't consider this ok unless you know you have interior-pointers.

[링크 : https://valgrind.org/docs/manual/mc-manual.html#mc-manual.leaks]

[링크 : https://stackoverflow.com/questions/24201561/valgrind-memory-leak-log]

누수는 누수인데 늘어나진 않는 누수인 것 같아서 일단 패스.

[링크 : https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/18]

기동 콘덴서 교체

구매하려다가 아부지가 여분으로 가지고 계셔서 받아오니 교체하고 보니 잘 돌아간다. 

(테스터기 좋은거 쓰셔서 1.2uF 짜리 용량 체크하고 받음)

그래도 아주 강하진 않지만 그런대로 쎄짐

그래서 교체한걸 보내드리니 0.8uF로 용량이 줄어있다고 확인해주심.