I am at a bit of a loss, I'll start by saying I am not a programmer by trade though I have written code for most of my life. My background is in IT, mainly networking. That being said I have written code in many languages and find it fairly easy to pic up new ones as it's typically just changes in syntax but logic is logic. Currently I am in charge of the code base for our controller which runs a mixture of basic and assembly for the low level stuff. My goal with Nuttx is to have a RTOS to run our control software which looks like it will have to be rewritten back into C or even C++. We have created a new PCIe board that replaces what we are currently using 5 pc/104 cards. Writing the driver for our PCIe card won't be too hard as I have written drivers for my previous cards before.
So At this point I have cloned the git repo and selected the PCI branch, installed the build tools, configured the system as qemu-intel64:nsh and successfully make nuttx.bin and nuttx..elf . At this point I am lost. The document I was reading then talks about loading to an arm device, and I can't find any information on setting up an AMD64 build on the actual hardware. So the first step at this point that I don't understand is how to get the system to boot using the complied nuttx.bin or .elf. Once I an get the system to boot I will need to be able to run a compiled program. I assume I will have to rewrite my little linux test program using nuttx. At it's simplest the test program can be hard programed to the correct bar address given by uefi and since it is on it's own but, no other devices are on bus 1, it should continue to be assigned the same bar address. This test program will really be as simple as turn on isolated bit, sleep, turn off sit, sleep again, repeat. This will allow me to test for jitter, in a true RTOS the outputted square wave will remain consistently the same. If the OS interrupts the process jitter will appear and can be measured on an oscilloscope. Once that test is complete and it passes I can help get the PCIe sections working and tested along with helping in other ways. I know the learning curve will be steep but I'm a pretty good climber. -----Original Message----- From: Robert Faron <robe...@cmslaser.com> Sent: Tuesday, July 28, 2020 2:52 PM To: dev@nuttx.apache.org Subject: RE: AMD64 arch >>One thing that would be important would be to understand what >>processor you are using. >If there is some specific hardware, I would also be willing to buy a board and >help out... although I am no x86_64 expert (I did do the i486 port some years >ago, but that is about the extent of that). I have yet to determine what hardware we will use. While testing and developing I am currently using an ASUS 855M-E. Just because I have it laying around. Though if an Intel 9th gen board is easier to acquire I could also change boards. -----Original Message----- From: Gregory Nutt <spudan...@gmail.com> Sent: Tuesday, July 28, 2020 1:21 PM To: dev@nuttx.apache.org Subject: Re: AMD64 arch > One thing that would be important would be to understand what > processor you are using. If there is some specific hardware, I would also be willing to buy a board and help out... although I am no x86_64 expert (I did do the i486 port some years ago, but that is about the extent of that). NOTICE: This e-mail message and all attachments transmitted with it may contain trade secrets and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by telephone at 407-679-9716, and delete this message and all copies and backups thereof. Thank you NOTICE: This e-mail message and all attachments transmitted with it may contain trade secrets and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by telephone at 407-679-9716, and delete this message and all copies and backups thereof. Thank you
