• State Answer Suggested
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 1899 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 Restoring NAND Flash

MRI
Expert 1130 points

I was restoring the NAND flash and updatting the kernel using the following commands:

EVM # setenv ipaddr 10.8.104.78
EVM # setenv serverip 10.8.104.79

EVM # tftp 0x80700000 uImage

EVM # nand erase 0x400000 0x200000
EVM # nand write 0x80700000 0x400000 0x200000

The FLASH was written ok, I didn't get an error, but now i can't usre the teraterm console on COM1. i get no response from the DVEVM.

  • 0
    TI__Mastermind 37340 points

    unfortunately I am not too familiar with DM365 yet, but if you are not seeing any UART output at all from EVM, I would suspect maybe u-boot was overwritten and is out in the weeds.  If possible with this EVM, I would try swtiching to UART boot mode and look for 'BOOTME' message in UART output; if you cannot even see this, then this may be a hardware issue.

  • 0
    TI__Mastermind 41665 points

    As Juan suggests, the usual cause for this sort of situation would be the UBL and/or U-Boot being inadvertently overwritten, however the commands you have look to be correct so I am not sure how that would have happened.

    Unfortunately as there is not yet a serial boot flash loading utility for the DM365 though when it is available it will be through here (I believe there is actually some code for it in the PSP 2.10.00.14 collateral though I have not tested it). This being said, at the moment to recover a board that is no longer getting into U-Boot you would need Code Composer Studio and an emulator, there are recovery utilities within /dvsdk_x_x_x_x/PSP_x_x_x_x/bin/dm365/.

  • 0 in reply to Bernie Thompson TI
    Prodigy 65 points

    I'm having the same problem, running the test programs from CCS, the Flash content was wiped out. It wouldn't be a big deal, since we are not using Linux. But I have a lot of connection problems, because of the missing startup initialization. The good part is, that the kernel does not start up, which sometimes prevented CCS to connect via JTAG sometimes :-)

    The biggest problem seems to be the missing flash utility ( the DM365 is not compatible with the others) and the bugs in the built-in boot code. USB-boot, SPI-boot, UART-boot, all are not working correctly. 

    Is there plan to come out with a new flasher tool ?

  • 0 in reply to Stefan Warnke
    Intellectual 650 points

    I have not had any problems with the DM365 EVM's NAND flash - the JTAG flashing went smoothly, and I've done multiple NAND upgrades, NAND boot-ups, JTAG erases, and they all have been particularly smooth.

    The only hiccup has been the unavability of the DM365 serial flashing toolkit, particularly due to the silicon bug preventing the UBL/RBL combo from running at 115200 (they run at some other baud rate).

    Jerry

  • 0 in reply to JerryJohns
    Prodigy 65 points

    Jerry,

    what tool did you use for flashing via JTAG?

    Stefan

  • 0 in reply to Stefan Warnke
    TI__Mastermind 41665 points

    Stefan Warnke said:
    I'm having the same problem, running the test programs from CCS, the Flash content was wiped out. It wouldn't be a big deal, since we are not using Linux. But I have a lot of connection problems, because of the missing startup initialization.

    What sort of connection problems are you having, and what sort of initialization issues? From an initialization standpoint are you using the gel file from Spectrum Digital?

    Stefan Warnke said:
    bugs in the built-in boot code. USB-boot, SPI-boot, UART-boot, all are not working correctly. 

    I have not done any work with the USB or UART boots, but the SPI boot mode on DM365 works, I have a modified EVM (for a larger SPI memory) that will boot the UBL out of SPI.

    Stefan Warnke said:
    Is there plan to come out with a new flasher tool ?

    I believe this is on the roadmap but I do not have any schedule, at the moment JTAG is the only practical way to go.

  • 0 in reply to Bernie Thompson TI
    Prodigy 65 points

    When there is no startup initialization code in the flash, the processor will execute whatever it finds. JTAG should be able to get him out and overwrite settings via GEL file. Thta's the theory.

    The GEL file we used was the one that came with the board but I also downloaded the latest from SD. Onecoworker still has a XDS510PP and we had to comment out the PLL initializations, because it was always hanging there. After the wipe out I exchanged the EVMs, because she was not able to connect at all with the 510PP anymore.

    My Signum JTAGJet (USB) is still able to connect and run the GEL file but I wanted to test some initialization code. We basically copied the GEL code into a startup function as C-code called first in main. This one is always ending up somewhere randomly, but not getting through. CCS disconnects at this point. Mostly it is best to exit CCS and maybe even power down EVM and emulator to get the system back. Otherwise it is all just half working.

    We are are still working on SPI boot, with UART and USB boot we definitely found problems. The built-in DM365 boot loader is not compatible with 355 or 6446, we worked before.

    Jerry, in my CCS 3.3 I only see Tools->Memory Save/Load Utility. Are you refering to this one? I thought it can only work with RAM and you would need some code write to the flash.