ROM Bootloader on DM6437 AIS question

Is this the proper forum to post this question?

Thanks,

~C

It seems that the SEEK value must be referenced from the Request CRC command. The value seems to be encoded in 2's complement and added to the address of the Request CRC command. However, I still can't get the DSP's ROM bootloader to jump to the location I want.

Anybody have any ideas? Does the bootloader in the ROM only allow jumping back, not jumping forward?

If anyone is interested, this is how I am programming the first few bytes of the flash:

#define AIS_CMD_SECTLOAD     0x58535901
#define AIS_CMD_REQCRC        0x58535902
#define AIS_CMD_ENCRC        0x58535903
#define AIS_CMD_DISCRC        0x58535904
#define AIS_CMD_JUMP        0x58535905
#define AIS_CMD_JUMPCLOSE    0x58535906
#define AIS_CMD_SET         0x58535907
#define AIS_CMD_STARTOVER    0x58535908
#define AIS_CMD_SECTFILL    0x5853590A
#define AIS_CMD_GET            0x5853590C
#define AIS_CMD_EXECFUNC    0x5853590D

const int MBR[] = {0x00000003,    // 24-bit SPI mode setup word
    0x41504954,  // AIS Script Magic Word
    AIS_CMD_EXECFUNC,  //Function Execute Command
    0x00030000,  //   Selects PLL configuration function, with 3 arguments
    0x00000015,  //   PLLM value
    0x00000000,  //   PLLDIV 0
    0x00000000,  //   Clock source
    AIS_CMD_EXECFUNC,  //Function Execute Command
    0x00090002,  //   Selects DDR memory configuration, with 9 arguments
    0x00000017,  //   DDR PLLM
    0x00000001,  //   PLL SRC
    0x0000000B,  //   DDR CLLK DIV
    0x00000000,  //   VBPE CLK DIV
    0x50006405,  //   DDR Control register mask
    0x00138832,  //   SDRAM Config register mask
    0x28923211,  //   SDRAM Timer 0 register mask
    0x0016C722,  //   SDRAM Timer 1 register mask
    0x000004EF,  //   SDRAM Refresh control register mask
    AIS_CMD_ENCRC,    // Enable the CRC Check to make a jump
    AIS_CMD_STARTOVER,    // Reset the CRC to 0
    AIS_CMD_REQCRC,  // Request the CRC to start the JUMP
    0x000000FF,    //    This is the expected CRC is 0x00000000, so we use any other value to make the jump
    JUMPSECT_BASE-0x50  //     This is the relative address that will be added to the current address, 0x1000 - 0x50
};

Thank you for posting your solution! I did not even catch that this thread was on here.

It does look like the SEEK will go off of the address after the SEEK value itself, I apologize for not catching this previously, this seems to be a bug/feature of the RBL, at least for SPI boot (I think NAND as well but I have not really dug into that code). What is happening is every time the AIS interpreter code reads a value from SPI the pointer it uses to read the value gets updated, the same pointer that you are adding the SEEK value to (!). I did not catch this previously because I was only looking at the AIS code and what it does with SEEK, which does not actually increment the pointer so it looks like you would be offsetting from the command as opposed to the value after the SEEK. So the AIS interpreter reads the SEEK value and by doing so moves the pointer ahead to the next word, thus when you add the SEEK value you are offsetting from the word after the SEEK value. The documentation is not very obvious that this is the case, it elludes to it by saying 'current address in AIS' which happens to be the address following the SEEK value. I intend to get this clarified in the documentation, as you suggest this may apply to other parts as well.