Error Sending Ram For Bootloader
Recent Activity Top Posters Your name or email address: Password: Forgot your password? Stay logged in Menu News News Quick Links Recent Activity What's New? Help Forums Forums Quick Links Search Forums Recent Posts Active Topics Gallery Gallery Quick Links Categories Explore User's Albums New Albums New Photos New Videos Collections Locations Cameras Streams Cloud Menu Log in Sign up Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches Recent Posts DroidForums.net | Android Forums & News Forums Android Discussions Android Hacking Android Hacks and Help why do i always get this error when using rsdlite to flash a sbf? Discussion in 'Android Hacks and Help' started by tktouch12, Mar 17, 2010. tktouch12 Active Member Joined: Nov 17, 2009 Messages: 1,240 Likes Received: 0 Trophy Points: 36 Ratings: +0 i've used it twice now (to go to ese53 and now back to 2.0.1 (so i can get the ota, then i'll root it)). both times it said failed, but really worked. it scares the heck out of me. its not a big problem if its actaully working, but why does it think its failing? and could this lead to a problem later? i looked in program files>motorola>rsd lite and found a couple flasherrorlogs i will attach, maybe they will explain it. is anyone else having this problem? thanks (p.s.- i know using rsd lite is bad, thats why i'm concerned, but i'm fairly fluent in using droid) its .log so i can't attach it, so here it is (i wish i knew how to quote something): 23:32:22, March 17, 2010 Line: 517 ERROR: AP Die ID: 0a80011843680304000000000400 23:32:22, March 17, 2010 Line: 524 ERROR: BP Die ID: 0000000000000000000000000000 23:32:22, March 17, 2010 Line: 531 ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff 23:32:22, March 17, 2010 Line: 538 ERROR: BP Public ID: 0000000000000000000000000000000000000000 23:36:16, March 17, 2010 Line: 919 ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR File: X:\test_dev_usb\flash\code\flashdll\RDLOp.cpp Device ID: 0 23:36:16, March 17, 2010 Line: 1182 ERROR: Phone[0000]: Fl
5 Likes Received: 0 Was trying to flash using RSD Lite version 4.8 and 4.9 even tried the latest moto drivers... It is failing at 97% with the following error 15:08:40, March 29, 2011 Line: 597 ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x1BE400 Command: ADDR (Error Code: e003003f), Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257 File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp Device ID: 0 When I boot up the phone I see: http://www.droidforums.net/threads/why-do-i-always-get-this-error-when-using-rsdlite-to-flash-a-sbf.30527/ Bootloader 30.04 Code Corrupt Battery OK OK to program Transfer Mode: USB Anyone have any suggestions on what I can do. I am using the 2.3.340 Official SBF file (VRZ_MB810_2.3.34_1FF_01.sbf) Thanks Advertisement Mar 29, 2011 #1 gmenfan83 Well-Known Member Joined: Jul 20, 2010 Messages: 1,409 Likes Received: 320 DragonMan said: ↑ Was trying to flash using RSD Lite version 4.8 and 4.9 even http://androidforums.com/threads/sbf-failure-need-help-please.308199/ tried the latest moto drivers... It is failing at 97% with the following error 15:08:40, March 29, 2011 Line: 597 ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x1BE400 Command: ADDR (Error Code: e003003f), Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257 File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp Device ID: 0 When I boot up the phone I see: Bootloader 30.04 Code Corrupt Battery OK OK to program Transfer Mode: USB Anyone have any suggestions on what I can do. I am using the 2.3.340 Official SBF file (VRZ_MB810_2.3.34_1FF_01.sbf) ThanksClick to expand... Try to redownload the sbf and try again ...it sounds like a corrupt download ....your rsd and drivers are fine if the program launches and gets to 97% complete Mar 29, 2011 #2 andronoob New Member Joined: May 25, 2010 Messages: 1 Likes Received: 0 My rds lite won't recognize the phone.Any thoughts? Mar 29, 2011 #3 DragonMan Member This Topic's Starter Joined: Aug 6, 2010 Messages: 5 Likes Received: 0 andronoob said: ↑ My rds lite won't recognize the phone.Any thoughts?Click to expand... Make s
(2 flash tries) Connect phone to computer http://forum.gsmhosting.com/vbb/2504438-post6.html USB port before proceeding Searching for phone... found S Flash Neptune LTE2, getting test interface... usb error 7 [5] Writing firmware "R479_G_08.B5.76R_PDS005_LP0003_DRM0101_VSTAM_SPAN ISH206BR_PORTUGUESE206US_ENGLISH206_JPJAVA_G_08_V3 i_01_01_07R_GSPSLQA1CTIARLA144_1FF[LOCKED].pcf": https://devzone.nordicsemi.com/question/34950/nrf51822-dfu-problem/ Loading RAM downloader for Bootloader Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x3FCA000 Command: ADDR Flash failed Finished with result error sending 0xE0030009: Phone[0002]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x3FCA000 Command: ADDR Writing firmware "R479_G_08.B5.76R_PDS005_LP0003_DRM0101_VSTAM_SPAN ISH206BR_PORTUGUESE206US_ENGLISH206_JPJAVA_G_08_V3 i_01_01_07R_GSPSLQA1CTIARLA144_1FF[LOCKED].pcf": Unable to connect to the Subscriber Unit. Unable to retrieve interface handle Unable to connect to the Subscriber Unit. Unable to retrieve interface handle Finished with result error sending ram 0x27 Searching for phone... found S Flash Neptune LTE2, getting test interface... usb error 7 [5] Writing firmware "R479_G_08.B5.76R_PDS005_LP0003_DRM0101_VSTAM_SPAN ISH206BR_PORTUGUESE206US_ENGLISH206_JPJAVA_G_08_V3 i_01_01_07R_GSPSLQA1CTIARLA144_1FF[LOCKED].pcf": Loading RAM downloader for Bootloader Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x3FCC000 Command: ADDR Flash failed Finished with result 0xE0030009: Phone[0002]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x3FCC000 Command: ADDR Searching for phone... found S Flash Neptune LTE2, getting test interface... usb error 7 [5] Writing firmware "R479_G_08.B5.76R_PDS005_LP0003_DRM0101_VSTAM_SPAN ISH206BR_PORTUGUESE206US_ENGLISH206_JPJAVA_G_08_V3 i_01_01_07R_GSPSLQA1CTIARLA144_1FF[LOCKED].pcf": Loading RAM downloader for Bootloader Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x3FE6000 Command: ADDR Flash failed Finished with result 0xE0030009: Phone[0002]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x3FE6000 Command: ADDR badillo View Public Profile Visit badillo's homepage! Find More Posts by badillo Page generated in 0.11273 seconds with 6 queries
2015-04-17 06:54:06 +0200 I built the GCC bootloader from source based on the suggestion of another user in this forum instead of using a precompiled hex file. The Softdevice is 7.1. It shows DfuTarg. And using nRF Toolbox, I can send a zip package of a new application. It works 100% of the time. The new application is using the same Softdevice and SDK. I added the Dfu service by using the reference code in ble hrs sample. Once that new application is sent, I can select its device name in nRF Toolbox in the DFU menu, and send the same zip application just to try a firmware update. However, with the application running, it fails 100% of the time. Upload failed : Gatt Error (133). With nRF Master Control Panel, the log shows : Error (0x81) : GATT Internal Error, then Error (0x85) GATT Error. I searched on google and this forum and I haven't found a problem similar to this. Here is the parameters I used : Linker script for bootloader : /* Linker script to configure memory regions. */ SEARCH_DIR(.) GROUP(-lgcc -lc -lnosys) MEMORY { FLASH (rx) : ORIGIN = 0x00035000, LENGTH = 44K RAM (rwx) : ORIGIN = 0x20002000, LENGTH = 0x2000 BOOTLOADER_SETTINGS (rwx) : ORIGIN = 0x0003FC00, LENGTH = 0x400 } SECTIONS { .bootloaderSettings 0x0003FC00 : { } .uicrBootStartAddress 0x10001014 : { } } INCLUDE "gcc_nrf51_common.ld" Linker script for application : /* Linker script to configure memory regions. */ SEARCH_DIR(.) GROUP(-lgcc -lc -lnosys) MEMORY { FLASH (rx) : ORIGIN = 0x00016000, LENGTH = 0x2A000 RAM (rwx) : ORIGIN = 0x20002000, LENGTH = 0x2000 } INCLUDE "gcc_nrf51_common.ld" Modified dfu_types.h #define BOOTLOADER_REGION_START 0x00035000 To create the init packet : nrf.exe dfu genpkg app.zip --application firmware.hex --application-version 0xffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0x5a At the end of ble_service_init: ble_dfu_init_t dfus_init; // Initia