I have included the Project Settings and Bit Test Build stage by editing the.p4 file in the.iobj subdirectory of your project. If you are familiar with IAR's Keil ARM development toolchain, you will see these settings are similar to what they provide in the \"Project\" section under the \"Build\" tab for a project.
When complete, the project should build and run successfully providing the usual USB, IAR, Keil etc. applications that we are used to seeing from Arm Cortex processors. For this example, we will explore IAR's \"Random Number Generator\" application. This is a real-time RNG application that will generate 64 bit, non-blocking, pseudo random numbers. IAR provides us with a starter project that does all the work for us.
The first thing to notice is the Keil Hex Viewer does not like the existence of the code or data. Adding an empty dummy file.asf will make it happy. I added the file to the iomem.c.obj file and commented out the code. The next thing to notice is that the Debugger does not like the SIMULATION code and triggers a runtime error. To silence it, we add r14 to the global volatile uint32_t Seed; and in our main loop we either set it to NULL; or to a known value of 0x12345678. This provides the seed for the pseudo random generator. Now that our project is complete and everything is building, let's compile it and see if it works (e.g. using the Keil Hex Viewer and Debugger). We should find that we can look at the buttons on the device (e.g.
I want to use USBMSD_SendData to send data to the device. On the ARM access unit, there is a file that maps Data Transfer Request (DTR) to Send Data (SD). The access unit is enabled when there is a DTR, but when there is nothing to send, there is no BK MSD_DataTransmit. 7211a4ac4a