Torpedo Wireless SOM Installing New Image

Create Account

Create Account

You are here: >> >> >>

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

Forums
Search Forum
Advanced SearchTopicsPosts

Prev Go to previous topic

Go to next topic

Last Post 02 Jul 2015 06:52 AM by Adam Ford

Torpedo Wireless SOM Installing New Image

3 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

Kyle Cote

New Member
Posts:6

01 Jul 2015 10:58 AM
I'm trying to load a new Image and deploy it on the Torpedo DM 3730 Wireless SOM through an SD Card. I currently have an image loaded and programmed into NAND that was based upon the default configuration "defconfig.new-bluez" to complete the initial Linux Bluetooth tutorial which I completed all the way through. Now trying to load an image based upon a new configuration in which I've only added a few files to the root file system I'm unable to load but the current image programmed in NAND opens up fine. The block where it's looking for the mmc1 shows it recognizes the card is there but is unable to read "boot.scr". I've tried this with two different SD cards as well as different image configurations that were both default and custom but I receive the same message. Any help in changing this would be great! Minicom Serial Output: Texas Instruments X-Loader 1.42 BSP-dm37x-2.4-3 for dm3730logic (2015-06-25 13:) DRAM: 256MB (ProductID defined) Booting from NAND NAND: in-chip ECC SgnP image: 0x6f160 bytes read from NAND at offset 0x80000 to 80400000 U-Boot 2011.06 BSP-dm37x-2.4-3 (Jun 25 2015 - 13:15:07) OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz Logic DM37x/OMAP35x reference board + LPDDR/NAND I2C: ready DRAM: 256 MiB Board: DM37xx Torpedo Enable battery backup charger (BB_CFG = 0x1c) NAND: 512 MiB NAND: Internal to NAND ECC selected Found '28' display panel In: serial Out: serial Err: serial Product ID data cached to: 40200000 Die ID #67e400029ff80000016b3a861800b01a OTG_SYSCONFIG: 00000001 - needs to be 00002001 ID data ROM : Gen 2 Model : dm3730 Torpedo Version Code : -30 Temp Grade : Commercial Max Speed : 1000MHz Part Number : 1023758 Model Name : SOMDM3730-30-2780AKCR-C Serial Number: 4214M00179 Data (writethrough) Cache is ON Net: smc911x-0 Hit any key to stop autoboot: 0 == Checking mmc1 for alternate boot script boot.scr == mmc1 is available reading boot.scr Unable to read "boot.scr" from mmc 1:1 == Script not found on mmc 1, proceeding with defaultboot == kernel_location: nand-part, rootfs_location: /dev, rootfs_type: yaffs Proceeds to load and start Image.

Adam Ford

Advanced Member
Posts:794

01 Jul 2015 12:58 PM
You have to interrupt the boot process when u-boot starts. You can do that by pressing any key. There is usually 3 second timeout unless you changed it. If you want too long, it will just boot from flash. Once you interrupt it, you get a u-boot prompt. From there, you should be able to 'run makeyaffsboot' again to reload the image from the SD card. adam

Kyle Cote

New Member
Posts:6

01 Jul 2015 03:07 PM
Thanks Adam for the response. This worked and I was able to load the image!

Adam Ford

Advanced Member
Posts:794

02 Jul 2015 06:52 AM
That's fantastic! Feel free to ask whatever questions you need we are here to help. Many people will be out of the office on Friday, July 3. I will be here in the morning until 11:30 central time. adam

You are not authorized to post a reply.

Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit