Using Sp Flash Tool
Tyrell Baskerville
I am in the process of bringing-up/debugging a new design which contains an AM3505. I'm experiencing a number of difficulties programming either the NAND Flash or the SDRAM using the Flash tool (v1.6). To that end, I am examining each block of my design in-turn.
I've modified the GPMC Configuration to support 8-bit NAND Flash (i.e. WRITE GPMC_CONFIG1_0 0x00000800 in configuration_custom_am35xx.txt). Is there any other changes that I need to make? Which memory options should I select? (HWECC, SWEEC, NAND ECC - ONFI Compliant NAND?).
Continuing on with our testing, we are still receiving the same response - "Waiting for 2nd". I spent a bit of time searching the forums for this same symptom and it appears to be a common problem. Perhaps I'm missing something, but I have not (yet) found an answer that seems to address our problem. I apologize if this question has actually been answered, but please allow me to ask it again with the specifics for our board.
So it seems likely that I either have the SDRAM mis-configured, or I have a physical problem with the SDRAM interface. I will study the configuration file as it pertains to the SDRC - any suggestions?
The discrepancy lies if the fact that I am using a single Micron MT47H128M16RT-25E. In other words, I have a 16-bit data bus interface to the SDRAM. The default configuration supports a 32-bit interface, so all the eval boards must contain 2 SDRAMs!
The second loader programs are pre-compiled when the flash tool is built. There are different versions based on the SDRAM size in the system. The program takes care of initializing clocks and SDRAM interface per the text entries in the configuration file. The 2nd loader also contains drivers for various flash memory types. For Sitara ARM we have only made use of the NAND driver. This allows flashing of the bootloader(s) and Linux kernel into NAND without the aid of a working U-Boot or Linux kernel for a custom board. The underlying program is a console application called OMAPFlash. The flash tool is actually a GUI application that wraps OMAPFlash. Starting with the AM389x (DM816x), AM387x (DM814x) and AM335x devices, the ROM boot loader has been redesigned to use off-the-shelf tools for booting, such as ordinary DHCP/TFTP servers and basic terminal programs with XMODEM / KERMIT file transfer capabilities. For AM335x a new flash tool is under development that makes use of the USB and Ethernet booting and flashing capabilities in U-Boot. The new flash tool will be available in 2Q13. See the preliminary user's guide here:
2. Where may I find guidance on the changes needed to both phases (xloader/MLO and "u-boot") of the u-boot system for hardware differences? I see that one input to this is include files from the Pin Mux utility, but what are the others? Is there, perhaps, a checklist?
2. Then download the MLO (xloader), u-boot, and uImage(Linux) onto the NAND flash at the offsets given in the Flash 1.6 User Guide, Example 2 for Micron NAND flash. Ensure that the MLO and u-boot are downloaded using the "X-Loader / U-Boot" 1-Bit ECC Layout, and that the uImage of the kernel is downloaded using "Kernel."
In order to obtain the root file system image, take one of the the tarballs from the "filesystem" subdirectory of the AM35127 SDK, unpack it into temporary directory as the root user, and use mkfs.jffs2 to create a .bin file of the directory as described in:
I think you have to install the old Edison drivers first. Emlid DOCS seemed to have removed that information which leaves users with older Reach products with no longer supported Emlid chips at a loss.
Hi @Charlie_Robinson, I have just been through the process of flashing my old reach modules to firmware 26 on a win10 machine. To get USB-to-PC connection I needed to disable driver signatures and then install EdisonDriverSetup1.2.1 as per this thread Flashing Reach RS - Win10
The flashing tool then found the module and completed the update without issue.
This tool is currently used to flash bootloaders onto MicroSD cards or eMMC modules exported as USB Flash drives.
sudo ./lft.sh bl-flash BOARD_MODEL BLOCK_DEVICE
Replace BOARD_MODEL with a model from ./lft.sh b-list
Replace BLOCK_DEVICE with a device from ./lft.sh dev-list
Please note that this tool may destroy GPT partition tables so we recommend that you back up any valuable data on the target device.
I have the aml-s905x-cc board. There is only one main device showing (mmcblk1) as my sd disk. When I try to flash, it says the the device is a not a valid target. Just a thought here and stupid question:
There are multiple buttons and switches on most boards. The button is for entering BootROM mode for very advanced vendor specific programming and recover. The switch (if present) is for enabling/disabling onboard UEFI BIOS.
I just downloaded the RME USB Series Flash Tool to update my RME UFX. Everytime I try to open it, it doesn't. Does anyone know what the problem is? I am running Mac OS X 10.9.2 on a 2x2.66ghz Quad-Core Intel Xeon. Thanks
Thank You FolkFreak. You know, I looked behind the unit and did not see the USB port next to the Firewire port. I even googled pics of the UFX and never saw the USB port in the pic. My eyesight must be going or I'm getting old. LOL. Thanks for your help. Your reply made me look at the back of the unit for a second time.
I had the same issue: the flash update tool did not want to open at all, thought the USB connections seemed to be alright (because I could play Mac OS sounds, iTunes, etc...). But I could not synchronise TotalMix FX nor open the USB driver utility.
The issue was only the I had previously switched my UFX in class-compliant mode in order to make it work with my iPad 2. When I switched off the class compliant mode, everything ran smoothly, the flash update tool ran without any issue.
There is actually a .deb file for the tool. I really have no idea whether it is official sony or just unofficial linux port. All I know is that there is a .deb file for the tool which installs the flash tool on ubuntu. That actually left me wondering if there is any way out for Suse.
Anyway my problem is, that I can't receive any ACKs and NACKs, because I just have a half-duplex connection. So I have to write my own flash tool. Additionally I want to write to my device without erasing the flash memory completely.
And flashing stopped with an error. Later i reflashed my device with earler version of MFT, but ALL data was LOST. I mean ALL INTERNAL MEMORY WAS ERASED. And internal sdcard is become only 9.7 Gb capacty (was 11.4).
I use Dell venue 8, I don't bother with this useless tool, I just use fastboot directly, to change size of partitions, edit partition.tbl to desired size, My dell system was set at 1024, which is too small when I use my cwm recovery to backup and restore system will fault out as system is too big to go back on 1GB partition, so choice is remove some junk from system or increase system partition size.
Once you partition and flash everything, boot to cwm recovery and resize partitions, use resize on cache, data, system, you need to umount cache first, cache may not need but try anyway, before reboot remount cache.
While some of what you say maybe true, I can't help but smile, you do know the only reason this thread exists is cause the tool failed? Had the tool preformed 100% correctly this thread wouldn't exist, if OP had just used fastboot like I posted above this thread again wouldn't exist.
So while you may think this tool is great, I don't to each our own, I am also waiting and for a response that I know will never happen, from intel, on this tool, would love to see them tell the OP to do almost exactly what I posted above.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I made the suggested adjustments in the safe startup mode, however can't get the RME USB Series Flash Tool.app to run. After double-clicking the application, it closes right away again and I don't see any messages in the Privacy & Security prefs.
since I used Apple's migration assistant tool when installing the computer from a previous machine with an M1Pro, it might also be that some remnants of the older drivers I used with a Fireface UFX are still somewhere?
The firmware update runs on all versions of M1/M2. But as it needs the driver, and the driver is not working as long as the device firmware has not been updated, it is necessary to first update the firmware of these interfaces using the former kernel extension driver!
If the firmware is really not up to date (v127 or v138 is current, depending on the hardware version) then you need to install the older driver v3.28a after following the instructions here: -usa.com/rme-macos.html
also I tried the steps described under rme.to/reset and once that was done, ran the Fireface USB 328A.pkg installer again, allowing the needed approvals in the OS X Privacy and Security settings, but no change.
is there a way to locate eventual remnants of previous RME installers, since I used Apple Migration Assistant - with the M1 Pro Mac that had the drivers for the Fireface UFX installed, as a source? Or should these have been taken care of with the command line given under rme.to/reset?
the power supply was faulty, I measured it last night and it only produced a little over 900mA, which apparently was just enough to light up all the control lights in the UC as usual, however not enough to make it properly connect via the USB port to the computer!
93ddb68554