HUA demo + ethernet boot on the EVM 6678?

Hi Alejandro,

The size seems to be really big. But I don't think that should matter. You can try reducing the size to check that for sure. Also after you connect, do you know where the program counter is? Also can you check if the boot magic address(0x87fffc) is populated correctly.

Thanks,

Arun.

Hi Arun,

thanks for replying. I have seen through CCS the content of address 0x87FFFc. The value is 0x80108D20, which according to my .map, corresponds to _c_int00. So, I think this is correct.
However, when I connect from CCS, I see that the PC register is at different locations like 0xD94E2EFC or 0xA71ED27C which do not map to any known memory position (according to my memory map)

By the way, when I run hex6x.exe simple.rmd I get the following output:

Translating to ASCII-Hex format...
   "hua_evmc6678l.out"   ==> .cinit     (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .text.1    (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .text.2    (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .const.1   (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .const.2   (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .switch.1  (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .switch.2  (BOOT LOAD)
   "hua_evmc6678l.out"   ==> .vecs      (BOOT LOAD)

and, since the output file (.btbl) is much smaller than the .out, and there are sections in the .out that do not show in the hex6x output (.nimu_eth_ll2, .far.1...), I wonder if hex6x could be missing some sections.

On the other hand, I have tried to reduce the size of the .out file as you suggested. Basically, I have written this program:


                #include <string.h>
                #include <stdlib.h>
                #include <ti/sysbios/BIOS.h>
                #include <platform.h>

                int main() { BIOS_start(); }

                void EVM_init()
                {
                    platform_init_flags sFlags;
                    platform_init_config sConfig;
                    memset( (void *) &sFlags,  0, sizeof(platform_init_flags));
                    memset( (void *) &sConfig, 0, sizeof(platform_init_config));
                    sFlags.tcsl = 1;
                    sFlags.phy  = 1;
                    if (platform_init(&sFlags, &sConfig) != Platform_EOK) {
                        while (1) {
                            (void) platform_led(1, PLATFORM_LED_ON, PLATFORM_USER_LED_CLASS);
                            (void) platform_delay(50000);
                            (void) platform_led(1, PLATFORM_LED_OFF, PLATFORM_USER_LED_CLASS);
                            (void) platform_delay(50000);     
                        }
                    }
                }

                int hpdspuaStart()
                {
                    int i, k;
                    for (;;)
                    {
                        for (k = 0; k < 4; k ++)
                        {
                            for (i = 0; i < 4; i ++)
                            {
                                platform_led(i, PLATFORM_LED_OFF, PLATFORM_USER_LED_CLASS);
                                (void) platform_delay(50000);
                            }

                            platform_led(k, PLATFORM_LED_ON, PLATFORM_USER_LED_CLASS);
                            (void) platform_delay(50000);
                        }
                    }

                    return(0);
                }

                uint8_t *Osal_platformMalloc (uint32_t num_bytes, uint32_t alignment) {    return malloc(num_bytes); }
                void Osal_platformFree (uint8_t *dataPtr, uint32_t num_bytes) {  if (dataPtr) free(dataPtr); }
                void Osal_platformSpiCsEnter(void){ return; }
                void Osal_platformSpiCsExit (void){ return; }

For linking I use the same flags/libraries as in the original HUA demo. This way the size reduces to 3.47 MB.
When I run this program through CCS, it works (the LEDs flash). However, when I try to send it via Ethernet for booting, it does not work: the LEDs do nothing and the state of PC register and boot magic address are similar to the previous case.

Any suggestions?

I have made some progress on this topic.

I have built the Example 2 from the BIOS_MCSDK_2.0 User Guide which consists of a BIOS program that plays with the LEDs (but with no NDK involved). The .out size is around 3 MB. The only thing I did not have was the rmd file used to convert the .out in a .eth that can be booted via ethernet.
I tried with this rmd file:

led_play.out
-a
-boot
-order L

ROMS
{
   ROM1:  org = 0x90000000, length = 0x100000, memwidth = 32, romwidth = 32
          files = { led_play.btbl }
}

which should use DDR3 and it works!

Then, I have been adding NDK support to the cfg file and what I have found out is the following:
When I put everything on MSMCSRAM, it works fine.
When I put a section on DDR3, it does not work.

For example, if I change
  Program.sectMap[".const"] = "MSMCSRAM";
to
  Program.sectMap[".const"] = "DDR3";

the program does not work. So, is it possible that I am not able to start the HUA demo from Ethernet because it has lots of sections on DDR?
I have read about a problem with revision 1.0 of the board (SPRZ334D.pdf, advisory 8) relating the PLL, and it says that there could be problems with DDR. Do you think this could be my problem?

Hi Arun,

first of all, sorry for the delay, but I have had some technical issues trying to post.

Thanks for the suggestion. I have tried the NDK hello world example with Ethernet boot and it did not worked.
Then I have changed the .cfg file, by replacing all instances of DDR3 with MSMCSRAM so that nothing went to DDR3 and now it works!

So, it seems that I have problems booting from ethernet when the program has someting placed in DDR3.
I think I will try to continue with the rest of my program, since it should fit in non-DDR3 memory, and when I can get a rev 2.0 board I will try again
just in case the problem is related to the PLL bug.

On the other hand, when I run it from CCS, I always run the GEL script, that seems to initialize some DDR stuff.
I wonder if it is possible that I have to make some similar initialization when booting from Ethernet...

Best regards Arun!