OMAP 4460GP Blaze Flashing/Booting Android Problem

Try rebuilding all the FS from the xloader to the Android FS then copy all the files to the SDCard as explained in the release notes in Omapedia for this release.

I am not allowed to record videos.

Update:

I haven't been able to make good progress.

1) I was able to load Android (from using another SD card with a good bootloader then switching to on my OMAP but I made changes and suddenly it wouldn't load Android once again.

1.a) chmod 644 all .rc files on the rootfs folder

1.b) chmod 644 all .ko files

1.c) made changes in init.rc

1.d) made changes in init.omap4blazeboard.rc

2) The bootloader from the SD card for the 4AJ.2.2 release still doesnt work for me. It must be the xloader since on the instructions it says its for 4470 but i ahve 4460. If that doesnt matter, I do not know what's causing the garbage characters.

3) I am still getting untracked pid ### exited on the log. What does this mean?

4) Also I chmod 644 the .ko files because it was also getting the insecure problems but now I am getting these:

[   10.964874] wlcore: Unknown symbol ieee80211_nullfunc_get (err 0)
[   10.972991] wlcore: Unknown symbol ieee80211_pspoll_get (err 0)
[   10.980468] wlcore: Unknown symbol ieee80211_register_hw (err 0)
[   10.988403] wlcore: Unknown symbol ieee80211_restart_hw (err 0)
[   10.995941] wlcore: Unknown symbol ieee80211_get_hdrlen_from_skb (err 0)
[   11.004577] wlcore: Unknown symbol ieee80211_stop_rx_ba_session (err 0)
[   11.012725] wlcore: Unknown symbol ieee80211_wake_queue (err 0)
[   11.020172] wlcore: Unknown symbol ieee80211_find_sta (err 0)
[   11.027587] wlcore: Unknown symbol ieee80211_roaming_status (err 0)
[   11.035400] wlcore: Unknown symbol ieee80211_queue_delayed_work (err 0)
[   11.043579] wlcore: Unknown symbol ieee80211_proberesp_get (err 0)
[   11.051696] wlcore: Unknown symbol simple_open (err 0)
[   11.058258] wlcore: Unknown symbol ieee80211_remain_on_channel_expired (err 0)
[   11.067138] wlcore: Unknown symbol ieee80211_rx (err 0)
[   11.080841] wlcore: Unknown symbol ieee80211_report_low_ack (err 0)
[   11.088836] wlcore: Unknown symbol ieee80211_iterate_active_interfaces (err 0)
[   11.097656] wlcore: Unknown symbol ieee80211_free_txskb (err 0)
[   11.105010] sr_class1p5_calib_work: mpu: Calibration complete: Voltage Nominal=1390000Calib=1330000 margin=0
[   11.106323] wlcore: Unknown symbol rfc1042_header (err 0)
[   11.106323] wlcore: Unknown symbol ieee80211_tx_status (err 0)
[   11.106323] wlcore: Unknown symbol ieee80211_stop_queue (err 0)
[   11.106353] wlcore: Unknown symbol ieee80211_ready_on_channel (err 0)
[   11.106384] wlcore: Unknown symbol cfg80211_find_ie (err 0)
[   11.106384] wlcore: Unknown symbol ieee80211_sched_scan_results (err 0)
[   11.106384] wlcore: Unknown symbol ieee80211_scan_completed (err 0)
[   11.106414] wlcore: Unknown symbol ieee80211_channel_to_frequency (err 0)
[   11.106414] wlcore: Unknown symbol ieee80211_unregister_hw (err 0)
[   11.106445] wlcore: Unknown symbol ieee80211_beacon_get_tim (err 0)
[   11.106475] wlcore: Unknown symbol ieee80211_hdrlen (err 0)
[   11.106475] wlcore: Unknown symbol ieee80211_cqm_rssi_notify (err 0)
[   11.106506] wlcore: Unknown symbol cfg80211_testmode_alloc_reply_skb (err 0)
[   11.106506] wlcore: Unknown symbol ieee80211_frequency_to_channel (err 0)
[   11.106536] wlcore: Unknown symbol ieee80211_queue_work (err 0)
[   11.106536] wlcore: Unknown symbol ieee80211_sta_ps_transition (err 0)
_____

Let me know what changes i need to do.

Sorry for late response.

The other day we found that 2 SDCard had the same issue that you described in previous post about not booting and showing random data.

It was fixed by doing next command to the SDCard from the PC.

dd if=/dev/zero of=/dev/sde bs=512 count=200000

if it doesn't work try increasing to 250000, the command is from next post

http://e2e.ti.com/support/omap/f/849/p/269068/953215.aspx#953215

About the other questions, I didn't faced those, but try fixing the SDCard in this way and check if issues are gone.

About the why of this fix, I can only think that some SDCard has a initial partition in hidden status, and when formated it is only erasing a second partition table that is not hidden, for some reason this happens, we tried to isolate it by using 2 different PCs, and one time it is corrected issue was not able to be reproducible again.

Hey Manuel:

I had many problems loading Android 4AJ.2.2 so I decided to go with 4Aj.2.5P2 since it has MLO for GP.

I am having problem with the following log:::

[    8.443267] init: skipping insecure file '/default.prop'
[    8.449890] init: skipping insecure file '/init.rc'
[    8.599060] sr_classp5_calib_work: smartreflex_core: Calibration complete: Voltage Nominal=962000 Calib=8220
[   13.011505] init: Timed out waiting for /dev/.coldboot_done
[   13.021697] init: skipping insecure file '/system/build.prop'
[   13.031341] init: Unable to open persistent property directory /data/property errno: 2
[   61.130767] HDCP: failed to load keys
[   61.130767]
[  128.005981] rproc remoteproc0: error -62 requesting firmware ducati-m3-core0.xem3

Also, whenever I do the 4AJ.2.5P2 OMAP4 Jelly Bean Release Notes instructions, I skip the whole section from preparing emmc images until the end. How important are they if you are booting from the SD card?

It could depend on what method are you following, either Fastboot or copying the files to the SDCard.

From the post you are doing Fastboot method, by reading this thread it is copying files to the SDCard.

I remember that I followed Fastboot methods for 4AJ2.2 and 4AJ2.5p1 and it worked ok for both, thinking about it the only thing is to modify mmc.c in u-boot to set userdata.img to 2GB (2048MB) and check that SDCard is cleaned using dd commands from previous posts. In this case you need to follow the eMMC procedure plus the changes in fastboot.sh to include the SDcard selection and correct format, indicated in the respective post.

If you are booting the SDCard copying the files then it follows the same principle following the steps from the post, other critical step is to replace the ducati-m3.bin from release binaries. Other idea or reference could be to use a 4GB, do not use a 8GB or greater.

I don't have access to a OMAP4 Tablet2 then I cannot debug the issue in parallel, but I could try to help you guiding from the memory if you post step by step issues, in either case you posted the same issue in a new thread that should help to get a answer.

I followed the instructions for 4AJ.2.5.P2 up until Preparing Android Binaries.

1. Then afterwards, I copied the u-boot, uImage and MLO to boot and the others to rootfs (configured SD Card)
2. I hooked it up on my 4460, opened my minicom... [garbage characters]
3. I used an SD card with a working bootloader and then added bootargs (with setenv... boot) and switched back the SD Card with the 4aj.2.5p2 sd card... [init problems]
4. i changed init.rc and init.omap4blazeboard.rc according to the link you provided
5. chmod 644 to rc files, 644 to default.prop, 644 to system/build.prop and 777 to /data
6. added ducati.bin (from other releases) to both the boot folder and the rootf/system/vendor/firmware
7. repeated #3 ... it works fine
8. i also managed to get the WiLink7 working

Ok, thanks for explaining.

You can try to clean and format the SDCard in a different PC, I explained the reason of this clean in previous posts, but some other points are that  you could use a value of 500000 instead of 250000, I remember I tried a small number and it worked increasing it a little more but I cannot remember the exact number, other thing to check is that boot partition to be fat32, you could use a Linux partition program creating the MS-dos disc first and then create the FAT32 partition setting boot flag and active flag, maybe a 50MB partition size, check the steps to change the geometry following the procedure from http://omapedia.org/wiki/SD_Configuration,

dd if=/dev/zero of=/dev/sde bs=512 count=500000

check that /dev/sde is the SDCard partition,

You may not need any change change in u-boot by now if you check only that x-loader runs first, most boot changes goes in the u-boot. If it boots the xloader ok then can try adding modified u-boot.

The SYSBOOT configuration should be ok because you are able to boot using the other SDCard.

About cleaning the SDCard 2 extra points, it should be in a different PC or format it using a Windows format command or UI interface, this to clean the fat partitions tables (both), something about OMAP BOOT ROM reading the second partition under some circumstances for what I remember of the TRM and some tools doesn't restart or clean the second partition by default.

I think that some reason could be if SDCard is 4GB and first partition table is using the 4GB that is FAT32 using 32bits per 4,000,000,000 bytes of size divided by 512 bytes per sector is  250,000, reason why using 500,000 or a greater value could help to erase the second FAT table. At least it is one reason I can think, maybe using 700,000 in previous dd command or some tools to erase and set to zeroes all the memory Card.

Please verify if this works for you and comment.

I modified the previous post to include the information about how to change the geometry, in my case I ran it without modifying the geometry but it is required.