Should we create screencast tutorials?
FeaturedSo, CrossStudio and CrossWorks are fairly complex programs. They must be, we work on them every day along with new board support, answering technical questions, creating new technology libraries, and making and consuming copious quantities of coffee.
Now, all of us in the office know how CrossStudio works. And we know how to get the best out of it. And we know how to debug and answer common questions, and we fund ourselves answering the same questions over and over again, pointing out the same menu items, creating the same set of instructions for customers. So, it's clear there are (perhaps) some things that could be done better with online screencast tuition rather than with a written manual that read whilst on the throne.
Therefore I'd like to ask whether this is a good idea or not? I think we'd probably enjoy it, but the end result won't look too professional as video editing isn't our day job. But at least we can ditch the tutorial and screenshots in the manual which are usually hopelessly out of date.
So, chip in and tell us whether this is something that we should do!
-
Go for it. Seeing a technique demonstrated rather than just reading about it can certainly be helpful, especially when one is first getting accustomed a new coding environment.
I wouldn't worry too much about the "professionalism" angle, I'm sure it will be fine. Although, I can imagine something like...
[Establishing scene. Long shot of a country lane in the south of England. In the distance we see a classic 60's Lotus 7 speeding towards us.]
[Cut to the car's interior. Close up of the driver shot from the passenger's seat.]
"Hello, I'm Paul Curtis of Rowley Associates. Today we're going to talk about configuring the CrossStudio editor."
[Exterior view from the lane as the Lotus speeds away. Music surging as it crests a hill on the horizon. Fade to black.]
It's not a cat video but it might have potential. ;-)
-
Writing the tutorial for a hypothetical processor is time consuming and effectively useless. A few short screencasts covering simple things like installing packages and getting going on an STM32 with CMSIS-DAP is more relevant. The first one I want to do covers setting up CrossWorks for parallel and unity building, the second is how to set up tracing and profiling. These are new features in CrossWorks 3 and a with a screencast it would be easier to set things out.
Yes, we can update the manuals or add additional content on the website. From our experience, customers *do not* read the manual! What they do is fire off an instant ticket to the helpdesk asking for things that are (a) in the tutorial they couldn't be bothered to go through or (b) in the manual that they couldn't be bothered to search or (c) ask where the online manual is because they can't find it or (d) don't search the knowledgebase for simple things such as what they are entitled to do with their license.
So, a few short screencasts covering the main features of how to do stuff with CrossWorks would be better for those that just can't help themselves with printed matter.
The manual is fine as a reference, but not as a tutorial on how to get things done.
-
Since a lot of designs are based on the eval boards, a quick tutorial on how to take an eval solution and run through the basic steps needed to create a new independent design (directory) and the files necessary to support that altered design. Using the new TCP or mass storage for example would cover quite a bit including the platform library.
-
We have discussed, internally, whether we should simply stop shipping templates for the New Project wizard and simply ship demo projects which you could load and "save somewhere else" so you can get started easily. So, in the case of TCP/IP or mass storage, you'd take something that looked like it works on an eval board, use inheritance-by-text-editor to save somewhere else, and use that as a base to start a project. This seems a bit more natural than using the New Project wizard to create you something that is main() and little else.
The Platform library is growing; I'm working on KL46Z devices as we speak, having completed the KL25Z device. And I expect to get to the Tower systems fairly shortly. Kinetis is quite nice in that most of the peripherals are consistent! STM32 is also very nice, but the families do have significant differences in some areas.
So, I think we should do the copy-project-to-get-started, it's just how we accomplish this.
-
This is a great idea! I have actually created some of my own for my customer. Here is a short one about setting the application memory map for use with a bootloader.
http://screencast.com/t/u2ZjkJWoP
P.S. I don't think I used the New Project Wizard since my first project.
-
Great idea.
And I second the comments about project configuration / memory management being a good subject for the first screencast.
And Pauls comment about shipping demo projects would be better than the templates? - I agree - what would be nice are a cross section of reasonably complicated projects that can be picked apart to solve any problems being encoutered.
-
Before expending too much energy on videos, is it worth looking at also organizing information so that a user would find these videos (or text writeups)? It is just one example, but say a user wanted to learn how to enable the new Clang compiler option on the v3 toolset. I happen to know that there is a YouTube video showing this, but a search for "clang" on zendesk shows absolutely nothing. Even the venerable rowleydownload.co.uk site has only two hits, neither of which is applicable.
-
New user here, found this old thread while searching for tutorials on Crossworks. Wanted to say it would be a very good idea to make some tutorial videos, in my case it almost cost Rowley a sale. When I started with microcontrollers I tried using Crossworks on several occasions and found it hard to comprehend as someone completely new to embedded programming. I then started using IAR Embedded Workbench as there was far more support on the net and YouTube for very green users. I am now working with Crossworks again as it makes more sense now that I have experience with IAR, and our senior programmer uses Crossworks (which makes it our companies standard). I can already see that Crossworks will be the better product. I would have used Crossworks all along if there were more videos on its use, it also would have been helpful to have a tutorial series on using it with a development target like a TI Launchpad.
Please sign in to leave a comment.
Comments
16 comments