[quote author="sqkybeaver"]There will have to be an additional revision of the board, however i have this on pause until some software are solved and we are sure we can use a 16bit sram, it is already at the max free eagle size, and would have be moved to a 4 layer or larger board to accommodation a 32 bit bus[/quote]
OK. Well, I know I dropped off the face of the world. So I just wanted to post a quick apology. If we could use ram and nand similar to the at91sam9260evk, then we would not have to use the expensive compiler to rebuild the files for the sam-ba.....
Hello Everyone. I feel I owe you all a serious apology. My work has kept me too busy. I believe this project could move forward if you could boot the initial atmel files with GCC. Without that, we are unable to program the flash with the at91bootstrap. Once that is done, U-Boot and linux will be relatively simple.
Ian, I don''t know. Without someone testing the previous directions, I do not have enough information. It sounds like the sam-ba applets need re-compiled for 16 bit ram, they are made for 32 bit. Buildroot, kernel, filesystem should be ok right now. Just have to get past at91bootstrap. (I can't remember if I did anything with U-Boot yet)
(Sorry, I'm too poor to order the parts for my own board at the moment. It really slows things down not having a board to test on.)
Quick question: To anyone (other than sqkybeaver) with an assembled board, can you connect with sam-ba?
Plug in power and usb to your board, plug usb into computer. Unless you already use sam-ba it will ask you for a driver. Windows Vista and newer require you to use CDC mode, XP will let you use usbarm0 mode. The CDC driver is in "C:Program FilesATMEL CorporationSAM-BA v2.10drv". After drivers are taken care of, try to launch sam-ba, select at91sam9260ek and the com port it is on.
The next part is from memory, so please forgive me if I don't get the wording exactly correct. Click the AT45 tab In the drop down menu of scripts, select Enable Dataflash (SPI0 CS0), the click go or whatever it says Then select Erase All.
If that works let me know. Do not load the boot file yet, as there is no way to disable the chip select line right now. If you get an error connecting to the board, please post it.
Please let me know it it works. In the mean time I will put the proper linux patch back in. I will generate proper at91bootstap patches and u-boot patches.
If u-boot works, then led2 should (but might not) turn on. You will also see text on the debug serial port. Interrupt the auto boot as there is no kernel or rootfs loaded.
Please let me know. If it does not work, it may be because the the at91bootstrap is not right. Things to watch for: If you can not get into sam-ba, then you may have to hold pin 4 (CS) on the at45 to 3.3 voltz so sam-ba will start. then remove the 3.3 volts. Also, I am not 100% sure that the ethernet info is correct in u-boot. a way to test is to plug in a network cable and issue the dhcp command to see if it gets an address.
*EDIT* I have committed the updated kernel patch. To recompile the kernel, go into the cn-robert-buildroot directory, do a git pull cd buildroot rm -rf output/build/linux-3.1 make
Kernel will now compile without a problem. *NOTE* the u-boot and at91bootstrap generated are not for this board. I am now working on those patches.
[quote author="sqkybeaver"]are there options for tuning the build process? i am compiling on an I7 and have plenty of power left during compile.
ill wait for the next update to run the next compile.[/quote] Depends on number of cores. If you have more cores, then you can turn up the number in "Build Options->Number of jobs to run simultaneously". You can set that to the number of cores you have. For example for the E10 project I work on, I set it to 4 (although my computer has 8), and it take about an hour to compile from a make clean. My wife's laptop has 2, and it takes about 3 hours to compile from a make clean. (This does not count the downloads, since they are already downloaded)
A Few notes: The first time you run it has to download sources Then it compiles a tool chain After all of that, it starts building stuff for the target device
Usually once everything is built, (for development purposes) you can just recompile single packages. Then you will want to do a make clean, and a make to ensure everything builds correctly.
Regarding downloads in the dl folder: I'm sorry I don't every mention them or think about them. Since I have more than one buildroot projects, I will make a symlink from /usr/local/src/download to the buildroot dl directory. That way I do not have 20 copies of the same file. *REMEMBER*: do not run any buildroot processes as root. run them as a regular user.
Just trying to give you plenty of info.
I will continue on u-boot in about 30 minutes. compile and post a link to download and try. IF the at91bootstrap and u-boot work, then I will create proper patches and update the git and buildroot directories.
[quote author="sqkybeaver"]i just pulled and will time the current build with 6 threads in vbox enabled. it took about 1/2 hour for the first build i did.[/quote] FYI: Kernel (uImage) and rootfs are for this board. The at91bootstrap and u-boot are not for this board. They are for the at91sam9260ek However, as I patch them, you can do a git pull a couple of commands and a make
[quote author="sqkybeaver"]the most i have been able to get is the RomBOOT message from the dbgu port.
not sure if i am missing something.[/quote] Well, apparently when I #define CFG_DEBUG, it is not enabling the debug statements. So Unfortunately that is of no help right now. I will work on u-boot tonight/tomorrow morning. (Also work on getting debug statements to work in at91bootstrap)
I will post more info files tomorrow. (I know I said that yesterday)
It looks like the at91bootstrap (dataflash mode) will work mostly unchanged.
*HOWEVER* Since BMS is ties to VCC, and there is no way to chip select line from the data flash, these is no easy way to get into sam-ba mode when you need/want to. On the at91sam9260ek, they use push button 4. If you hold down button4 on powerup, it will erase the first sector of dataflash (at91bootstrap). That way you can get into samba.
I can change this so that either PC0 (X4-10) or PC1 (X4-9) can cause the same action. That way you put a jumper from GND (X4-8 and X4-7).
What do you think? Which do you prefer? I only picked those pins because there are close to GND pins on the header.
Status: at91bootstrap almost all done. kernel ready to test rootfs (jffs2) ready to test Now I need to work on u-boot.
go into sam-ba, connect, enable at45 dataflash, erase all, send boot file and select this file. I will work on u-boot shortly. This version of the dataflash has debug turned on, so you should see it saying starting at91bootstrap on the debug uarts (X4-5 RX and X4-3TX). Please let me know if it works or not. I will work on u-boot.
You can pull at any time you want.... Right now it is the basic buildroot with minor mods. In accordance to buildroot recommendations: buildroot/board/dp/robert/ will contain all linux patches, linux config, u-boot patches, and at91bootstap patches. (Plus and root-additions or post-build.sh) For now dangerousprototypes was too long and shortened to dp, I initially used robert, but that was before I dug into the kernel and got dp1arm9. I can change either of these, no big deal. I am about to commit the linux patch. Then move onto at91bootstrap.
*just commited buildroot/board/dp/robert/linux-3.1-patches/ * this patch will change.
[quote author="sqkybeaver"]to start off with i'd like a memory test, possibly something that can be used for a self test during manufacture.[/quote]
I understand that. The best way I know HOW to do that is by loading up at91bootstrap, then u-boot. From u-boot it is much easier to test memory with a "u-boot application". Also u-boot will then allow you to to load images over ethernet. Obviously this is not a full test of the PHY, but will let you know if it works.
I have a couple of questions and frustrations as I am working through linux kernel patches. (Yes, I work backwords. Kernel -> U-boot -> at91bootstrap, as the information flows better that way for me).
I will update my repo when done with current iteration of kernel patch. I have modified arch/arm/tools/mach-types with this line: dp1arm9 MACH_DP1ARM9 DP1ARM9 3833 I have modified arch/arm/mach-at91/Kconfig with: config MACH_DP1ARM9 bool "dangerous prototypes first linux compatible board" help Select this if you are using a dangerous prototypes first linux compatible boardl. 91sam9260 <http://dangerousprototypes.com/docs/Robert:_AT91SAM9260_Linux_development_board > I have modified arm/arm/mach-at91/Makefile with: obj-$(CONFIG_MACH_DP1ARM9) += board-dp1arm9.o
I copied board-sam9260.c to board-dp1arm9.c and making the appropriate changes. Using schematic to collect most information. However, I do have a few questions: Debug uart is hooked up, and will be ttyS0 as default and for console uart 0,1,2 are hooked up and will be ttyS1, ttyS2, and ttyS3. (Uart4 not wired to anything) I only see 1 usb host port hooked up (as opposed to 2 in the 9260evk) The usb device port has the vbus pin on PA26 (as opposed to PC5 on the 9260evk) no audio devices, so removed from board info DataFlash is on bus 0 with chip select 0 Without digging into datasheet (yet) it appears the mmc is not on SPI0 CS1. No Nand flash, so ripped out
Now the Questions: I do not see the phy_irq_pin, it is PA7 on the 9260 EVK. Is there a phy_irq_pin? Is the PHY RMII? I added LED1,LED2, and LED3 to PC31, PC30, and PC29. With led3 initially setup in heartbeat mode. Do you want more pins setup as leds? Do you want any GPIOs setup as buttons? Are there any I2C devices onboard to add to kernel? (RTC, EEPROM, etc)
Once I know the ethernet stuff ESPECIALLY, I can work on U-Boot.
i have a semi complete board, it will connect to the sam-ba with usb and serial.
the build time is really reasonable on the vm i have set up at home.[/quote] @sqkybeaver, I dont know how familiar you are with buildroot, at91bootstrap, u-boot, and every thing else....
I can add people as contributors. Tonight (currently 4:17 pm where I am now) I will patch at91bootstrap, u-boot, kernel, etc. Tomorrow morning I should have working patches and builds. I will post them someone (with a link).
Feel free to clone that repo, then in the morning do a pull. This is essentially a fresh repo with no modifications yet. I am about to go through sch, so I can get the GPIOS, network, flash, etc.....
I wish I would have known about this thread earlier. I am VERY VERY familiar with at91bootstrap, u-boot, and buildroot. FWIW: do not use ubuntu 11.10 to do the buidlroot compiles. ubuntu 11.04 and 10.10 work just fine though. (Debian, fedora, centos should work too)
I currently maintain custom buildroots for an at91sam9g20-evk, at91sam9g20 (custom board), at91sam9g45 (custom board), and atngw100.
Unfortunately I have not ordered my parts yet, *BUT* I am willing to build these for you. Also, If a few people need shell access to my build system I can set that up. (Dual Xeon E5310, 10GB ram, plenty of HD space) I would want a username, and a ssh public key (for login). Then I can setup a random password you can change on first login. Just email/PM me. (https://github.com/jcwoltz/E10-buildroot
At this point I think a github repo would be worthwhile for tracking changes to the buildroot environment and allow multiple collaborators. It doesn't matter to me if I set it up, or someone else does and adds collaborators. (Then put final uImage/rootfs/bootstrap/u-boot into dangerous prototype SVN). The reason I recommend git for this is the ease git can format and create packages.
I can build a at91bootstrap, u-boot, minimal uImage, and rootfs tonight. (as a starting point). The only thing that will take a little bit of time is so I can comb though the sch to make the board-robert.c file that contains flash mappings, gpio mappings, etc.
