No debug console IPNCDM355-VCA1

rblode said:

root = / rootfstype = dev/mtdblock3 rw ip = dhcp yaffs2

it should be: root=/dev/mtdblock3 rw rootfstype=yaffs2

Also care about writing you command in a single line! If you copy this string from Getting Started Guide (page: A-2), there will be some "newline" commands in it.

yes I noticed that the command is not good, but the problem now that there is nothing that works

rblode said:

the problem now that there is nothing that works

What do you mean by this? Does the system boot up with default bootparameters? If yes: What are default parameters? You can read them out by using "printenv"

non there is no boot , i connect the IPNCDM355 with the serial port and i see anything in the conole (No Uboot)

This is odd; normally, the primary reason you would not see any u-boot prompt in the serial console (assuming good cable is connected and PC serial console program is properly configured) is if u-boot got earsed or overwritten.  I do not see anything in the u-boot changes you described above that would do this. 

I would verify to make sure your PC serial console program is properly configured to grab data from the right serial port and is enabled.  If possible, I would even try a different program just to double check.  Otherwise, we may need to consider reflashing u-boot onto EVM.

Juan Gonzales said:

This is odd; normally, the primary reason you would not see any u-boot prompt in the serial console (assuming good cable is connected and PC serial console program is properly configured) is if u-boot got earsed or overwritten.  I do not see anything in the u-boot changes you described above that would do this. 

I would verify to make sure your PC serial console program is properly configured to grab data from the right serial port and is enabled.  If possible, I would even try a different program just to double check.  Otherwise, we may need to consider reflashing u-boot onto EVM.

I tested the serial port and the configuration with other equipment and it worked very well, I think I have the Uboot crashed or there is a hardware problem.

To flash Uboot I must have a JTAG? Is that there are other  means?

well, I am not too familiar with IPNC hardware, but on our EVM, you can flash via JTAG, UART port (see http://wiki.davincidsp.com/index.php/Serial_Boot_and_Flash_Loading_Utility ) or SD Card (see http://wiki.davincidsp.com/index.php/DM3xx_SD_card_boot_and_flashing_program ).  I am not sure if these tools would work with IPNC.

Juan Gonzales said:

well, I am not too familiar with IPNC hardware, but on our EVM, you can flash via JTAG, UART port (see http://wiki.davincidsp.com/index.php/Serial_Boot_and_Flash_Loading_Utility ) or SD Card (see http://wiki.davincidsp.com/index.php/DM3xx_SD_card_boot_and_flashing_program ).  I am not sure if these tools would work with IPNC.

Thnak you Juan , i will try this.

Hello ,

I solved the problem with the JTAG and CCS, the following procedure:

Burning UBL and U-Boot using CCS :
                  To burn UBL and U-Boot for DM355 IPNetCam:
                  1) Connect JTAG to IPNetCam debug board as shown.
2) Open Setup Code Composer Studio version 3.2 or higher.
3) Load evmdm355.gel file from <installDir>/bin/ directory.
4) Connect Code Composer Studio to the target board. You can also press
   Alt+C. The message “The target is now connected” appears as shown.
5) On the File menu, select Load Program. Load
   <installDir>/bin/NAND_programmer.out file.
6) Press F5 to run NAND_programmer.out file.
7) In the Standard Input dialog box, enter the UBL file path for ublDM355-
   nand-XXXX.bin file. Click OK. UBL binary is loaded to target board.
8) Enter the U-Boot file path for u-boot-1.2.0-dm355_ipnc-u-
    X.X.X.bin file. Click OK. U-Boot binary is loaded to target board.
9) Enter the Diagnostic file path for DM355_DEB.bin file. Click OK.
    DM355_DEB binary is loaded to target board.
10) Wait until Nand program completion message is displayed on Code
    Composer Studio message window.
11) When UBL and U-Boot are effectively flashed on DM355 IPNetCam
    board, disconnect the Code Composer Studio from the target board.
12) Power off and power on to reboot the NAND board.

Flashing Linux Kernel by UART on U-Boot :
             1) Use the following command at the U-Boot prompt:
                loadb 0x80700000
                The HyperTerminal window is displayed.
             2) On the Transfer menu, select Send File. The Send File dialog box is
                displayed.

3) In the Filename: textbox, type the uImage binary file path, ti-
   davinci/arch/arm/boot/uImage. From the Protocol list, select
   Kermit.
4) Click Send. Files are transferred to the target DM355 IPNetCam board.
5) Use the following command to load ramdisk to the target board:
   loadb 0x82000000
6) In the Send File dialog box, in Filename box enter
   <installDir>/bin/ramdisk_ipnc_X.X.X.gz path of the ramdisk
   binary file. Use Kermit as the transfer protocol.
7) Click Send. Files are transferred to the target DM355 IPNetCam board.
8) Copy uImage and ramdisk from RAM to NAND using the following
   commands:
   nand erase 0x200000 0xd00000
   nand write 0x80700000 0x200000 0x200000
    nand write 0x82000000 0x400000 0xb00000
9) Use the following command at U-Boot prompt:
    setenv bootcmd 'nand read 0x82000000 0x400000
    0xb00000;nboot 0x80700000 0 0x200000;bootm 0x80700000'
    setenv bootargs 'mem=80M console=ttyS1,115200n8
    root=/dev/ram0 rw initrd=0x82000000,10M ip=dhcp
    eth=00:11:45:11:03:55
    v4l2_video_capture=:device=MT9P031'
    This will set the kernel command line option.
10) Use the following command at U-Boot prompt:
    Saveenv
    This will save current environment variable setting to NAND.
 1) Use the following command at U-Boot prompt:
    boot
This will reset the device for using the new kernel
12) Press Enter and login as root. Kernel prompt is available.

Thanks Juan for pitching in and helping the customer on this question for the IPNC. I somehow missed this post earlier :(

Regards,

Anshuman