View source for Talk:Jetson TK1
- [View source↑]
|Thread title||Replies||Last modified|
|Factory refresh / wipe of Jetson TK1||1||21:41, 7 September 2016|
|please delete as dupe, could not find way....||0||05:43, 18 September 2014|
|size of page||1||05:39, 18 September 2014|
|Test||0||18:55, 21 August 2014|
|Tutorials openCV||1||20:33, 14 August 2014|
|Magazine about Jetson TK1||4||20:30, 14 August 2014|
|Mini-PCIe: Half vs. Full||3||00:15, 4 August 2014|
|which CSI-2 MIPI cameras are supported?||3||19:20, 28 July 2014|
|eMMC 8Gb?||2||19:08, 28 July 2014|
|"a micro-B to female Type-A adapter is included"||1||01:20, 15 July 2014|
I noticed the wiki has a link to NVIDIA for the reflash/wipe instructions. However, those instructions are woefully inadequate and send noobs on a wild goose chase for information on how to actually do it. I would suggest creating a page here which organizes and simplifies the step-by-step instructions (including the setup of a virtual machine or host linux machine). IMHO, if you're not breaking (and bricking) things then your not learning! Therefore, wiping the board clean and starting from scratch is one of the first things people should learn how to do. I'd be happy to contribute what I've found and learned so far as a starting point for this much needed "how-to" guide.
Sorry for not noticing this message. If you can contribute that page then yes it would be great!
could this page be broken into say 6 separate pages?
there is far too much information to my mind.
pages might be: home, hardware features, set up, tutorials, reference information, projects
in this way it may be easier to see what information is available.
this may be better both to help further organise, and most significantly for the new guest.
My answer to the "Tutorials openCV" still applies here: The idea is to have a single "landing page" for Jetson TK1 that is full of links to various things related to Jetson TK1. If we put just 1 link on the landing page for a whole set of tutorials, my guess is that many users will not notice the link and then assume there aren't tutorials available. So I prefer to keep most things linked to directly from the single landing page.
I think that for now the large landing page is good because it shows pretty much all the Wiki content available for Jetson TK1. But as more pages & projects & tutorials & info are added, I agree that it will eventually be better if it is split up into many separate pages. But for now, I prefer to keep it as a single page with links to pretty much everything. This is the same way that many of the other boards are done on this site, such as:
- Official Beagle Bone Black (Beagleboard:BeagleBoneBlack)
- Community Beagle Bone Black (BeagleBone_Community)
- MinnowBoard Max Minnowboard:MinnowMax
So I think this is a good solution right now. When our Wiki does become larger, then it would be a good idea to split it to many pages, like the massive Rasbperry Pi Wiki is done (RPi_Hub), but our community & Wiki size is still much much smaller than RPi and even much smaller than Beagle Bone Black & MinnowBoard Max, so I think we should follow the method of the smaller Wiki's for now. If you want, we can organize a poll on the DevTalk forum to see if users prefer a single landing page vs separate sections, and if they mostly prefer separate pages then I'll happily re-organize it. Do you like this idea?
You do not have permission to edit this page, for the following reasons:
- The action you have requested is limited to users in the group: Users.
- You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
You can view and copy the source of this page.
Return to Thread:Talk:Jetson TK1/Tutorials openCV.
The idea is to have a single "landing page" for Jetson TK1 that is full of links to various things related to Jetson TK1. If we put just 1 link on the landing page for a whole set of tutorials, my guess is that many users will not notice the link and then assume there aren't tutorials available. So I prefer to keep most things linked to directly from the single landing page.
The user "peepo.com" mentioned that there is no Jetson TK1 magazine for things like community projects. Currently Jetson TK1 is way too young to have enough of it's own content for a magazine, but eventually it would be a good idea. For now, the main place to look at would be CUDA projects, CUDA magazines, CUDA articles, etc, of which there are quite a few. There are even regular CUDA meetups in many cities around the world. Eventually when Jetson TK1 (and future Tegra based boards) has a larger community of users and contributors and projects, there would be similar things available for it.
There is precious little support for Jetson, outside nVidia, so you best not lose the little you have...
wiki is a different medium to forum, and the one I chose. please do not 'own' this wiki or it won't be a wiki.
wiki acts as a medium of record, I had no wish to enter into a discussion on a forum. which at this time as you suggest would not be effective.
It's true that Wiki and forums are different mediums, suited to different types of content. That's why I moved your question + request onto something suited for discussion like this Talk page or the DevTalk forum or on the Google+ community for general discussion), rather than a Wiki page that is supposed to be showing encyclopedia-style information, not questions or requests from users. If you want to add a section to the wiki about Jetson TK1 related magazines and you just say that no magazine currently exists, then that would make sense on a Wiki, but posting a complaining question onto a Wiki is not the correct method.
I regularly maintain this Wiki to make sure the content is fairly consistent and good quality, hence why I moved your question + request to the talk section. If I knew which user you were on DevTalk I would have moved it to the DevTalk forum so others can comment (eg: maybe a user actually does want to start working on a Jetson TK1 or Tegra magazine), but I wasn't sure if you use DevTalk so I posted it here instead since you obviously do read this Wiki.
Why was the magazine section added back? Why have an empty section (on the leading page, mind you) just to say there's no magazine?
In my mind, this wiki and it's projects section (hopefully to grow & expand over time), *is* the magazine.
I agree with Dustin, that we shouldn't put a magazine section if we don't have a magazine and if there are still not enough projects to make a magazine. Peepo.com, I want to remove the magazine section from the Wiki, but you clearly don't. How about we make a poll on the DevTalk forum (that hundreds of people will read, instead of this Talk page where just a handful of people will read), asking what the majority want:
1) Remove the Magazine section on the Wiki (until perhaps in >6 months time when there are enough projects to make a magazine)
2) Keep the Magazine section on the Wiki that says there is no Magazine.
3) Keep the Magazine section on the Wiki and start organizing to actually make a magazine about Jetson TK1 & CUDA. This would have to mostly be done by users with many user-contributed projects. I assume this won't be possible until atleast 6 months when Jetson TK1 is more in use).
Under hardware features / mini-PCIe, there are several links to products which are Full length (50.95mm) expansion cards, and will not directly screw onto the board, since it's mounting holes are for half-length (26.8mm) cards. There does exist 1 adapter/riser that should allow full-length cards, at additional cost. Propose to split adapter list to emphasize which would require an adapter (different sub bullet point). Or perhaps only hyperlink to cards that have been tested and known to work?
Thanks for the info Spawnflagger, I wasn't aware of this when I wrote those links. Actually none of the cards I linked to have been tested on Jetson TK1, I only know that at NVIDIA they tested a few mini-PCIe cards and those did work but I don't know what cards they actually tested. So I just did a search of various mini-PCIe cards and posted links to them.
I'll move the links to a separate page "http://elinux.org/Jetson/mini-PCIe" with the info you posted here, and keep full-height and half-height mini-PCIe cards in separate sections. If you end up finding other useful half-height mini-PCIe cards, feel free to add it to that page, mentioning "(untested)" or "(tested)" if you do actually test one. (Note that some devices will need kernel or firmware driver support before it works).
Thanks Shervin. I will be getting a Jetson TK1 soon, and have also ordered a Syba half-mini PCIe Gigabit NIC (Realtek based). I'll report back to confirm/deny that it works. The full-card to half-slot adapter/riser I mentioned is this MM3U+DB3U (untested).
I created it now at "http://elinux.org/Jetson/mini-PCIe"
Please could we have a list of supported cameras? with links to suppliers would be handy...
I've bought into a few boards over the years, which had CSI-2 MIPI connectors, but no cameras were supported.
it seems clear that currently not one CSI-mipi camera is known to work with Jetson,
Jetson TK1 is a very new board, so I'm not aware of anyone that has built a CSI MIPI camera adapter for it so far. But the Tegra K1 SOC is already used in numerous phones, tablets & Google's Project Tango, all of which use atleast one CSI MIPI camera, so clearly CSI MIPI cameras are supported. The problem is that there isn't a single CSI MIPI format, so you need to design custom hardware & firmware & software for each specific CSI MIPI camera you use.
TK1 is sold to public, ie me... public has no means to "design custom hardware & firmware & software for any specific CSI MIPI camera"
there is an expectation that one or more CSI cameras will be available.
see Raspberry Pi.
I agree that ideally a built commercial CSI camera board should be tested on Jetson TK1 and documented, but unfortunately NVIDIA has not done this and might not do it for many months or years since big customers won't want to use the same specific CSI camera board, and makers will be happy enough to use a cheap USB webcam, so NVIDIA hasn't made it a priority.
PS: Raspberry Pi did release a CSI camera board after the RPi became hugely popular, but Raspberry Pi is also about 100x more popular than any other embedded ARM board, so they have more reason to work on things like this, whereas Jetson TK1 is still very new & unknown so NVIDIA hasn't put many resources into add-on devices as yet. Hopefully this will change in the next 1 or 2 years, particularly for CSI camera & Arduino support!
$ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 12G 6.8G 4.4G 62% / devtmpfs 850M 4.0K 850M 1% /dev none 4.0K 0 4.0K 0% /sys/fs/cgroup none 175M 656K 174M 1% /run none 5.0M 0 5.0M 0% /run/lock none 874M 76K 874M 1% /run/shm none 100M 32K 100M 1% /run/user /dev/mmcblk1p1 30G 17G 14G 56% /media/ubuntu/GOPRO
this is as received...
Hmm perhaps upon delivery (with R19.2?) it has been formatted as 12G. However if you flash according to the directions it will reduce to 8G. I think this is to reduce the flashing time over USB.
Yes Dustin is correct, we ship it with 12G but if you follow the custom Linux flashing instructions it gives you a smaller partition since it can take an extra hour or so of waiting for that extra 4GB of space during flashing. We are likely to simplify it so that both the shipped device and the custom instructions give you a single 12-13G partition.
Quick Start Guide and physical item supplied is not female, but male micro-b to male A USB.
What purpose does this lead have?
Can someone please check with nVidia and advise?
The lead may be for connecting to another PC?
Early Jetson TK1's were sold with both a micro-B USB cable (to flash the device) and a micro-B to female USB-A adapter cable (to have a second USB 2.0 port). The adapter cable was later removed from sold devices for a while (since someone at NVIDIA thought it wasn't too important), but I think future Jetson TK1's will be sold including the adapter cable (since I convinced people that it actually is important!). So some customers received that adapter cable for free while some customers didn't.