ghi-electronics / docs Goto Github PK
View Code? Open in Web Editor NEWThis is the (unsupported) old docs. Click on the link for the new docs repo:
Home Page: https://github.com/ghi-electronics/Documentation/
License: Apache License 2.0
This is the (unsupported) old docs. Click on the link for the new docs repo:
Home Page: https://github.com/ghi-electronics/Documentation/
License: Apache License 2.0
Make sure the basics for the FEZ is there
Instead of alpha/beta/RC
Probably to the Cerb family document
Talk about how the latest 4.1 can be found in the 2016 R1 SDK for example.
Add links to the sam-ba and ST DFU tools that the installer requires for them to install manually before the SDK so we can remove the downloads folder on the new GHI site.
Mention the different Visual Studios and that they can still do 4.1 with VS2013.
http://docs.ghielectronics.com/hardware/legacy_products/netmf/intro.html
The MS docs site for example has a drop down box with the entire ToC
Should be internet_of_things.md. Make sure to update any pages that link to it.
FEZ Connect, FEZ Touch, music shield, Cobra display, E-Blocks, FEZ Mini Robot Kit, and any others.
WriteString and Flush(byte[]) coming soon
all products now link to ghi_bootloader.md#loading-the-firmware and they need to be updated to the TinyCLR Config page instead.
Keep legacy folder for ToC and intro, but move the actual products up to the hardware folder. That way we don't break any links when moving a product to legacy, we only move its ToC entry.
Just talk about our capabilities, move CANxtra there.
Manual: http://old.ghielectronics.com/downloads/man/File_System_User_Manual.pdf
Schematic was here: http://old.ghielectronics.com/catalog/product/428
Other resources found here: http://old.ghielectronics.com/support/file-system
It needs to be explained in the datasheet that BOOT0 and BOOT1/PB2 need to be pulled in the correct direction according to the Reference Manual under Boot configuration. It needs to also be noted that BOOT0 is inverted on our SoM so if you pull the pin low, it will be high and if you pull the pin high, it will be low.
Currently it just has UCM, SCM, TinyCLR, and Legacy. Make it instead:
UCM | SCM
TinyCLR | FEZ
Legacy | NETMF
In MODULES.HTM the code example for Button the pin assignments are reversed.
Document indicates LED on FEZSpider.GpioPin.Socket4.Pin3
and Button on FEZSPider.GpioPin.Socket4.Pin4
According to the schematic the LED is on Pin4 and the button is on Pin3
Not just expand. Rename the intro.md pages to index.md and have the group headers point there instead of listing them explicitly.
Probably need to list as one big ToC, see https://raw.githubusercontent.com/dotnet/docs/master/docs/toc.md
Mention what's coming for 1.0 and what will be after
Pending outcome of the test, 32 vs 16.
Maybe include nucleo?
In the document:
"To activate bootloader v2, set PA15 pin low." should be "To activate bootloader v2, set PC1 pin low."
Use the old docs to get going http://docs.ghielectronics.com/software/tinyclr/tutorials/gpio-change-writer.html
Want to give customers more information to design their own PCBs with SO-DIMM socket for UCMs.
Should say shields down at the bottom of /hardware/fez/intro. The page it links to is correctly called shields.
See ghi-electronics/TinyCLR-Core#26
For this we just need details on the ports side of it, make sure to highlight debugging an interop built in as well (dynamically loaded needs to be handled later once we support that).
https://blogs.msdn.microsoft.com/vcblog/2018/01/10/debugging-an-embedded-arm-device-in-visual-studio/
https://blogs.msdn.microsoft.com/vcblog/2017/10/23/arm-gcc-cross-compilation-in-visual-studio/
Use G120 as an example
For UC2550 and UC5550. Currently just two each, with and without WiFi. Should break out the differences in each one. Flash or not, RAM size, connectivity options, etc. Clarify in the intro that the specs vary, see available parts for details.
Touch pins for G400D in spreadsheet are not included in pinout table in docs.
the 4MB external is a non-stock option. WiFi is the only stock orderable.
Need to rebuild against the TinyCLR libraries, should be able to use the new HttpWebRequest without changes.
http://docs.ghielectronics.com/tinyclr/downloads.html
First table, bottom row, second column "trying" is spelled "tying."
Also, "provide" should be "providing."
-Joel @ GHI
To the FEZ Cerberus document
Should make clear that you may have to hold the LDR0 (BOOT B) signal down for a couple of seconds after releasing the RESET button to activate the bootloader. Applies to all UCMs and SCMs.
Will need to update the supported pages to not link to the firmware and instead mention the source. See http://docs.ghielectronics.com/software/tinyclr/boards/netduino.html for example
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.