ghi-electronics / documentation Goto Github PK

Change EnableExternalHeap() to ExtendHeap(), explain better

http://new-docs.ghielectronics.com/software/tinyclr/tutorials/usb-cdc-winusb.html

http://docs.ghielectronics.com/hardware/sitcore/soc.html

find and replace COM with UART everywhere!

Need to update.
Also say that we also support MSB/LSB on SPI.

We need to document what formatting is supported. For example, is this a bug or not supported?

https://forums.ghielectronics.com/t/are-spi2-and-spi5-available-on-sc20260d-dev-board/22974/8

private static void BugForGus()
        {
            for (Double i = 0.0; i < 10.0; i += 0.1)
            {
                Debug.WriteLine($"i = {i:F1}");
                Thread.Sleep(50);
            }
        }

update external flash section on https://docs.ghielectronics.com/software/tinyclr/tutorials/external-memory.html page.

Remove the code showing direct read write and instead explain how 8MBytes out of the 16MByte external flash is used for Deployment, just like the internal secure deployment. Since QSPI is not secure, a hacker can just pull out and read, we have "Secure" flag you can add to AssemblyInfo which tells the system that this specific assembly must be in the internal secure flash. The system will automatically locate assemblies and will try to put everything in the internal flash but when teh internal flash is full, it will start moving assemblies not marked as "Secure" to external memory, if available.

There is a flag to enable External flash that can be set in software or set using TinyCLR Config tool. Even if QSPI is found, the system will not use it till the user opt in.

We support 2 specific part numbers, document part numbers. If a customer is add their own QSPI then need one of the 2 we have tested.

Visual Studio clearly shows what assemblies are secure when deploying.

Finally, the other 8 MByte of flash is now reserved for future use.

We have a simple example to play samples on DAC but we need to show the library we have that actually decode WAV files

the table should show GPIO and other peripherals count. Update both website and docs.

Document number of rounds (32). Point to https://en.wikipedia.org/wiki/XTEA.

see this https://forums.ghielectronics.com/t/infield-update-of-firmware/23037

IFU does not care where the memory is coming from. In normal cases, the user will need to use unmanaged memory to allocate a large buffer enough to hold the firmware. If the user extended the heap to use external memory, the user can then use the regular heap.

The sample code can simply try allocation from unmanaged heap, if failed then try regular heap. The rest of the code will still be the same.

Document the new features:

1. Flash map
2. Configuration Flags

More details and screenshots for the page.

SignalGenerator is one example.

• Ethernet, ENC: Requres MacAddress from user, or exception
• Wifi: Option. If user pass Mac Address, use it, other than that, will use default from wifi module itself.
• PPP: No need MacAddress as some research. Whatever user set or not, don’t use and show as 00:00:00:00:00:00

Document its importance and where to get one for internal testing and where to get one for public use.

WiFi already has one built in but how ot use it?

Does PPP care fro MAC?

https://forums.ghielectronics.com/t/need-help-with-a-couple-of-quirks-with-visual-studio/23068

http://docs.ghielectronics.com/hardware/sitcore/soc.html

clarify which UART is for debugging, perhaps a special section just for this.

See ghi-electronics/TinyCLR-Libraries#612.

We need a page discussing/clarifying USB C. All boards now have USB C, which is great but it is a new technology that come with flaws! If you use USB A to USB C cable then all work ask expected but if you use USB C to USB C cable we have had some interesting results. Most USB C hubs do not work (only when using USB C to USB C cables of course.

https://forums.ghielectronics.com/t/uarts-and-interrupts/23086/3. Also explain how peripherals such as UART don't use GPIO interrupts and don't limit user interrupts.

https://docs.ghielectronics.com/hardware/sitcore/som.html needs 32MByte in the compare table and move both external ram and flash to be the highest 2 items in the compare table

... on individual SoMs, boards and chipsets

Just need to delete them in example. Those are not need in PPP.

I replaced :
var keyboard = new Keyboard(e.Id);
var mouse = new Mouse(e.Id);
var rawDevice = new RawDevice(e.Id);

by :
var keyboard = new Keyboard(e.Id,e.InterfaceIndex);
var mouse = new Mouse(e.Id,e.InterfaceIndex);
var rawDevice = new RawDevice(e.Id,e.InterfaceIndex,e.Type);

Hello,

Could you add somewhere the maximum allowable frequencies for the different SPI buses, please ?
I presume that they are not all on the same prescalers.

http://docs.ghielectronics.com/software/tinyclr/tutorials/gpio.html
This note needs to be moved to its own subsection, called "Pin Interrupts". The note on that page is not enough to this very important piece of info!

Input events use interrupts (IRQs). Interrupts are only available on 16 pins at any given time. Of those 16 pins, the pin number must be unique. For example: PA1 and PB1 cannot both be used as interrupts at the same time. However, PA1 and PB2, or even PA1 and PA2, can be used simultaneously with interrupts.