Hello, Im pretty much new at ARM, i have been playing arround a few weeks wih a Project in which i have a SAM9x35.
I´ve connected to the hardware with SAM-BA already. And today i Wanted to configure U-Boot Variables. (U-Boot is suposed to be installed, because all i did was following a guide from the person who started the proyect who is "gone" now).
With my Hyperterminal i access to the next Log, when kit starts:

As i Understand i should be prompted to press ENTER key for stoping the Booting and get acces to U-Boot. But it seems im running on a Primary Lvl Bootsrtap from ATMEL(AT91Bootstrap). Which basically is that i dont have U-Boot nor another seconday Bootloader.
Am i Correct? If that the case, i wont be able to chec MAC or IP adresses and consequently i wont have ETHERNET access to the board. Are All these asumptions correct?
Any Idea of how could i save the kernel plus the rootfile system bins with samba?
Well thanks and i hope you can help me.
Regards

U-Boot (normally) does not execute silently, and does output its banner to the console when it starts.

AleFachini wrote:With my Hyperterminal ...

There are much better terminal-emulator programs available than that, e.g. PuTTY, and TeraTerm.

AleFachini wrote:As i Understand i should be prompted to press ENTER key for stoping the Booting and get access to U-Boot.

No, the U-Boot prompt is for any key (that generates a character code).

AleFachini wrote:But it seems im running on a Primary Lvl Bootsrtap from ATMEL(AT91Bootstrap). Which basically is that i dont have U-Boot nor another seconday Bootloader.

AT91Bootstrap is the conventional second-level boot program on Atmel SoCs.
The convention is for AT91Bootstrap to load and execute U-Boot (which would in turn load the kernel), but recent versions have the capability to be built to load alternate programs including the Linux kernel.
BTW your oddball terminology and abbreviations/misspellings are distracting.

AleFachini wrote:If that the case, i wont be able to chec MAC or IP adresses and consequently i wont have ETHERNET access to the board. Are All these asumptions correct?

No.
Old(?) kernels had a dependency on U-Boot for Ethernet initialization.
Presumably it's been fixed, but I've never bothered to test it.
However you seem to be in a perfect situation to test with whatever version you have installed.
IOW if you're going to make a hypothesis, then instead of asking for validation, test it yourself.

AleFachini wrote:Any Idea of how could i save the kernel plus the rootfile system bins with samba?

"Samba" (the protocol) or SAM-BA?
Can you boot the board, and get a shell prompt?
Do you have network access?
Can you attach a removable storage device, e.g. USB flash drive or SDcard?

well the hardware board has an "adapted" Ethernet port to a RJ11 connector (4 pins) and i dont know if the cable is "normal" or "Crossed" but ill have to make one RJ45 to RJ11 adapter cable. Have Any suggestion on this point?

Yes, you are misinterpreting a flash memory map.
The layout of a storage device does not specify/dictate the order of execution of programs.

Refer to the Linux4SAM web page on the conventional Atmel AT91SAM9 Boot Sequence.
The left side lists the execution order of boot programs.
The right side describes the physical memories involved and the transfer of code & data. The NAND map that you reference is represented by the "Boot Media" at the top right.

AleFachini wrote:the later (SAM-BA)

The ability of the board to connect with SAM-BA depends on activating the SAM-BA Monitor on the board.
Refer to your SoC datasheet for what has to "fail" in order to execute the SAM-BA Monitor.

AleFachini wrote:I tried but no. Please Refer to code snnipet. this contains the log from Rs232

That boot log does not indicate any salient errors.
The console is enabled for the framebuffer.
Networking is enabled. A ssh daemon is started. The IP address might be static.
Did you try typing on the terminal, as that sometimes triggers getty to reissue its output?

AleFachini wrote:... and the program boot cant be stopped or at least I dont know how.

You're not comprehending what I wrote.
Your board does not execute U-Boot when it boots from NAND.
There is no mechanism to interrupt the NAND boot sequence on your board as it is currently configured.

AleFachini wrote:well the hardware board has an "adapted" Ethernet port to a RJ11 connector (4 pins) and i dont know if the cable is "normal" or "Crossed" but ill have to make one RJ45 to RJ11 adapter cable. Have Any suggestion on this point?

100Base-T uses only two twisted pairs, but you'll have to figure out what kind of nonstandard connector wiring you have.

If you're unable to guess the hostname or IP address for a ssh login, then you may have to use Wireshark.

AleFachini wrote:Yes it does, although i did not got to this yet. I´ve read about being able to overwrite or even boot from sd cards.(really not much idea of this)

IMO booting the board using an external device is the most-straightforward method of inspecting and copying the contents of NAND and the rootfs (assuming that's your goal).
On the SAM9X35 booting from SDcard has precedence over NAND, unless the BSC register is used to inhibit that.