uEVM Flashing issues.

Hi Martin,

It seems that the size of iboot is incorrect..To work properly It should be set to 48KB , instead of 23KB (as its printed):

sudo ./usbboot -f 
waiting for device... 
reading ASIC ID CHIP: 5430
rom minor version: 01 IDEN: 0000000000000000000000000000000000000000 
MPKH: 0000000000000000000000000000000000000000000000000000000000000000 
CRC0: 06e92275 CRC1: 00000000 
device is GP 
using built-in GP iboot of size 48-KB 
sending 2ndstage to target... f0030002 
waiting for 2ndstage response...
received 2ndstage response...

So, the GP iboot size is determinate by "iboot_gp_size" depending on  the platform used - OMAP4 / OMAP5 (look usbboot.h).

Please, make sure you are building for panda5.

Attached is correct usbboot for reference.

3884.usbboot.tar.gz

Hi Martin,

I tried the usbboot from Panda5AJ.1.4_Release_Notes and this problem also appeared at my setup.

I can recommend using Panda5AJ.1.3_Release_Notes- thou there is a slight error for usbboot part - there is no such commit like:

71f4037a947416a6d40b5cae28180d65512d701c .

You should checkout to branch "/origin/p-master-dev-es1" In order things to work. And after building, you should copy manually the file "out/omap5uevm/omap5uevm_GP_MLO" to "emmc_files/omap5uevm_GP_ES1.0_MLO" because otherwise the "fastboot.sh" script will fail.

In this case also size of 23K is reported, but you can re-flash the panda board as  many times you need.

Regards,
Tsvetan

Hi Martin,

You should also notice that Release 1.4 is referenced for HW Platforms TI OMAP5 5432 uEVM ES2.0 only.

Please, check your version and use the correct usbboot.(You can find it on the back of the box ).

For ES1.0 you should check out branch "/origin/p-master-dev-es1" ,

for ES2.0 you could checkout to commit "0a929aa1d947da06a2277135eceab58664973300"

Hi,

Please provide the exact command line syntax to checkout "/origin/p-master-dev-es1"

Thanks,

David

Hi.

 I can't speak to the validity of the code but here is the syntax for checking out a git branch.

$ cd ~/git/omapboot/

$ git checkout origin/p-master-dev-es1

If you don't already have the git tree then you'll need to clone it

$ git clone git://git.omapzoom.org/repo/omapboot.git

-Martin

Hi,

I have encountered the same "waiting for 2ndstage response..." problem as mentioned at the top of this thread, except I've used this recipe: http://www.omappedia.com/wiki/Panda5AJ.1.5_Release_Notes.

I have replaced the usbboot file using the supplied file in the post above which successfully changes the GP iboot size to 48kb, but as mentioned before, it doesn't proceed just as before.

For my development, I am using virtual maching Ubuntu 12.04 LTS inside Windows 7. It seems like this could be a driver issue, and perhaps the Release Notes failed to mention a necessary ADB configuration. Using the "sudo ./adb devices" or "sudo ./fastboot devices" commands, this yields a blank list of devices. Forgive me if I'm completely off track here, but after following the Release Notes and TI video regarding installing the pre-built binaries, I cannot duplicate their success.

Best,

James

Hi Martin,

I was experiencing the same problem, but I was able to reach the "2nd stage received" point and then proceed to install the pre-built binaries. Here is what I did to accomplish this.

1) Installed the following libraries onto my Ubuntu 12.04 system using the command "sudo apt-get install ia32-libs" based on details found here (http://ubuntuforums.org/showthread.php?t=1923932).

2) Followed the instructions found here (http://developer.android.com/tools/device.html) to add the device ID (found by using command "lsusb") to the rules file. Afterwards, I restarted the "udev" as described here (http://stackoverflow.com/questions/9210152/set-up-device-for-development-no-permissions).

I was then able see that my OMAP5430 was recognized by using the "./adb devices" command (the list of devices was blank previously).

Best,

James