Linking problem with pico-SAM9G45

I am not using the LCD touchscreen, so I can't help you there, sorry. We tested the LCD touchscreen with the Android image for the Pico, and it worked, but I have no need for the LCD touchscreen.

It's definitely possible to put your app into the pre-built image, but, so far, I have not worked on this, so I do not how to do it yet. You can use the "scp" command instead, it can load your app to the sd card - then you can duplicate the sd card as needed.

Originally Posted by magickernel Hi, I would to use the linux pre-build image, if possible, to put inside the sdcard, some "app", like "helloworld.c", so that they can be performed on board, and the output can be visible on the lcd touch. The app is stand-alone. So, I see in the angstrom, is available the arm-eabi-gcc, it's is the only mode to run the app ? So, the file app can be load on a subdir of the pre-build image ? Please, can you help me, thanks ?

Hi Jeff, how are you ?
So, regarding the point 3, can you explain the steps to acquire the ip board ? I try with the wireshark software, but the tool not visible the ip address of the board...or maybe I forgotten any step before ?

From windows xp, I try with dhcploc command....: it's possible, but, howto define the range ip in the command ?

Thanks.
I'm waiting your suggestions... :-)

Originally Posted by imperialbeachdude Hi Marco - I understand that you have built the simple helloworld app, and now you need to get it on the board. I am responding here so others may see the steps we took. There are several options possible, I will list them below. 1. Have you successfully built the SD card image using the instructions from the pico wiki page? You must get this done for anything to work. We finally used WinImage on a Windows XP box to do this, but there are several ways. You cannot get anything done unless you get this completed correctly. 2. Have you built a TTL to RS232 converter to attach to J7 on the board? It's not very hard, but it is not my area of expertise, you will have to find someone else to help with that. I do recommend building the converter, as it is the debug port used by the kernel. This is not absolutely required, but helpful. When the board is booting, you will see output on this port, so you will know if you got step 1 done properly, as it will boot correctly, and you can login as root from the debug port. 3. Even if you do not get #2 done, the board will still boot if you got step 1 done, and you can connect to it through your local network. To do this you will need the IP address of the board, by default the board uses DHCP. You can look at your DHCP server after the board boots - it will be listed in the DHCP client table. Or, you could use Wireshark with a port monitor switch and watch the IP traffic from the device, and discover it's IP address that way. After you discover the IP address, it is a normal Linux login, for example ssh root@192.168.1.113 (assuming the board came up at 113). Then you can use scp to load programs to the board. Let us know if you get the app loaded - good luck! Jeff P.S. Have you considered using the BeagleBoard instead? My understanding is there is a lot more support and documentation for the BeagleBoard than the pico board.

Hi there -

The easiest way to discover the IP address of a device on your network is to look at the DHCP client list in the router on your network. This is simple to do on a small network - login to your router, and look at the DHCP client list, and identify all the devices connected to your network. If the pico board is working correctly, it will be one of the devices, and you can "ssh" to the device. If you are on a large corporate or academic network, this may be impossible without help from your IT department. In that case you should purchase an inexpensive router and make your own private network, with just your computer and the pico board attached. It's also possible to run a dhcp server directly on your computer, and then plug the pico board directly to your computer - but I think that is more complicated than the first solution.

Jeff

Originally Posted by magickernel Hi Jeff, how are you ? So, regarding the point 3, can you explain the steps to acquire the ip board ? I try with the wireshark software, but the tool not visible the ip address of the board...or maybe I forgotten any step before ? From windows xp, I try with dhcploc command....: it's possible, but, howto define the range ip in the command ? Thanks. I'm waiting your suggestions... :-)