Uncompressing Linux... done, booting the kernel. [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.0.1-23108-g97cebce (gcc version 4.4.3 (GCC) ) #13 SMP PREEMPT Mon Aug 29 12:34:05 EDT 20 11 [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387f [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: OMAP4 Panda board [ 0.000000] Truncating RAM at 80000000-bfffffff to -afffffff (vmalloc region overlap). [ 0.000000] Reserving 20971520 bytes SDRAM for VRAM [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] OMAP4460 ES1.1 [ 0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000 [ 0.000000] PERCPU: Embedded 7 pages/cpu @c0d91000 s6848 r8192 d13632 u32768 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 188160 [ 0.000000] Kernel command line: console=ttyO2,115200n8 mem=1024M androidboot .console=ttyO2 vram=20M omapfb.vram=0:16M androidboot.serialno=0146A5490E00E016 androidboot.bootloader=U-Boot_1.1.4 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 741MB = 741MB total [ 0.000000] Memory: 743880k/743880k available, 42552k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB) [ 0.000000] vmalloc : 0xf0800000 - 0xf8000000 ( 120 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .init : 0xc0008000 - 0xc0041000 ( 228 kB) [ 0.000000] .text : 0xc0041000 - 0xc05ea000 (5796 kB) [ 0.000000] .data : 0xc05ea000 - 0xc063e580 ( 338 kB) [ 0.000000] .bss : 0xc063e5a4 - 0xc07866b0 (1313 kB) [ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, N odes=1 [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] NR_IRQS:410 [ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_c k. [ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz [ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 13 1071999ms [ 0.000000] Calibrating delay loop... 1392.74 BogoMIPS (lpj=5439488) [ 0.007873] pid_max: default: 32768 minimum: 301 [ 0.007873] Mount-cache hash table entries: 512 [ 0.071624] Initializing cgroup subsys debug [ 0.071624] Initializing cgroup subsys cpuacct [ 0.071716] Initializing cgroup subsys freezer [ 0.071777] CPU: Testing write buffer coherency: ok [ 0.071960] twd_timer_setup: no clock found [ 0.071960] Calibrating local timer... 341.51MHz. [ 0.117431] L310 cache controller enabled [ 0.117431] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x5e470000, Cache si ze: 1048576 B [ 0.193695] CPU1: Booted secondary processor ... ... ... [ 6.857238] Alternate GPT is invalid, using primary GPT. [ 6.862976] mmcblk0: p1 p2 p3 p4 p5 p6 p7 [ 6.867462] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 6.876586] voltdm_scale: No voltage scale API registered for vdd_mpu [ 6.883422] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1317000 v olt [ 6.891265] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=92 0000000, v=1317000] [ 6.900695] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 6.910064] voltdm_scale: No voltage scale API registered for vdd_mpu [ 6.916931] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1025000 v olt [ 6.924743] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=35 0000000, v=1025000] [ 6.934295] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 6.941772] voltdm_scale: No voltage scale API registered for vdd_mpu [ 6.950256] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1380000 v olt [ 6.952209] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=12 00000000, v=1380000] [ 6.968231] cannot apply mgr(lcd) on inactive device [ 6.968322] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 6.968353] voltdm_scale: No voltage scale API registered for vdd_mpu [ 6.968353] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1380000 v olt [ 6.968383] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=12 00000000, v=1380000] [ 7.006652] omapfb omapfb: failed to apply dispc config [ 7.015228] cannot apply mgr(tv) on inactive device [ 7.020446] omapfb omapfb: failed to apply dispc config [ 7.028991] cannot apply mgr(lcd2) on inactive device [ 7.034423] omapfb omapfb: failed to apply dispc config [ 7.043029] omapdss DPI: Could not find exact pixel clock. Requested 74250 kH z, got 76800 kHz [ 7.054687] regulator_init_complete: VANA: incomplete constraints, leaving on
[ 7.062255] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.071441] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.078308] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1025000 v olt [ 7.086242] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=35 0000000, v=1025000] [ 7.095703] regulator_init_complete: CLK32KG: incomplete constraints, leaving on [ 7.104797] regulator_init_complete: VDAC: incomplete constraints, leaving on
[ 7.112823] regulator_init_complete: VCXIO: incomplete constraints, leaving o n [ 7.121520] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 7.128448] Freeing init memory: 228K [ 7.135650] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_s core_adj instead. [ 7.168334] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.179168] usb 1-1.1: new high speed USB device number 3 using ehci-omap [ 7.187164] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.194183] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1317000 v olt [ 7.217254] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=92 0000000, v=1317000] [ 7.249023] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.258148] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.258148] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1380000 v olt [ 7.272857] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=12 00000000, v=1380000] [ 7.312164] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 [ 7.320312] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber =0 [ 7.330963] smsc95xx v1.0.4 [ 7.347381] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. O pts: (null) [ 7.381835] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.391021] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.398284] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1025000 v olt [ 7.406524] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=35 0000000, v=1025000] [ 7.416076] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.425811] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.432739] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1025000 v olt [ 7.441101] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=35 0000000, v=1025000] [ 7.446166] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0- 1.1, smsc95xx USB 2.0 Ethernet, 2e:3d:fb:66:65:07 [ 7.462829] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.471954] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.478790] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1380000 v olt [ 7.483306] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=12 00000000, v=1380000] [ 7.591430] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.591430] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.607360] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1025000 v olt [ 7.615386] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=35 0000000, v=1025000] [ 7.624938] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.624938] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.640899] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1380000 v olt [ 7.647277] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=12 00000000, v=1380000] [ 7.749389] omap_vp_get_curr_volt: PMIC function to convert vsel to voltagein uV not registerd [ 7.758544] voltdm_scale: No voltage scale API registered for vdd_mpu [ 7.765380] platform mpu.0: _dvfs_scale: Unable to scale the mpu to 1025000 v olt [ 7.773223] platform mpu.0: omap_device_scale: scale by mpu.0 failed -61[f=35 0000000, v=1025000] [ 7.782745] omap_vp_get_curr_volt: PMIC function to
...
> On 09/21/2012 11:11 AM, scherb...@gmail.com <javascript:> wrote: > > Anybody please help me, I used this manual > > http://omappedia.org/wiki/4AI.1.4_OMAP4 ... anda_Notes > > <http://omappedia.org/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Panda_Notes> > > for building my android system and I finished this. But, when I input > > sdcard in pandaboard es, I have this error: > [....] > This is not so good idea,first,I used pandaboard es,second,my problem in > that ,I mean, "omap_vp_get_curr_volt: PMIC function to convert vsel to > voltagein
uV not registerd" and "voltdm_scale: No voltage scale API registered for vdd_mpu ".
>> > for building my android system and I finished this. But, when I input
>> > sdcard in pandaboard es, I have this error:
>> [....]
>> This is not so good idea,first,I used pandaboard es,second,my problem in
>> that ,I mean, "omap_vp_get_curr_volt: PMIC function to convert vsel to
>> voltagein
> uV not registerd" and "voltdm_scale: No voltage scale API registered
> for vdd_mpu ".
вторник, 25 сентября 2012 г., 16:23:54 UTC+3 пользователь dmitry pervushin написал:
> On 09/25/2012 12:27 PM, scherb...@gmail.com <javascript:> wrote: > > Are you getting that log when using the binaries you built? > > What if you use the prebuild binaries?, is it working?
> > Yes, why I should use prebuild, if i have build binaries? > That's simple - because prebuilt binaries are tested. I am trying to > reproduce your problem, but I failed to...
> -- > Sincerely yours, > dmitry pervushin
Stop, I compiled the kernel and other I needed files, format the memory card using fastboot recorded it all on the card. And received an error. I I had no prebuild files.
> вторник, 25 сентября 2012 г., 16:23:54 UTC+3 пользователь dmitry
> pervushin написал:
> On 09/25/2012 12:27 PM, scherb...@gmail.com <javascript:> wrote:
> > Are you getting that log when using the binaries you built?
> > What if you use the prebuild binaries?, is it working?
> > Yes, why I should use prebuild, if i have build binaries?
> That's simple - because prebuilt binaries are tested. I am trying to
> reproduce your problem, but I failed to...
> --
> Sincerely yours,
> dmitry pervushin
> Stop, I compiled the kernel and other I needed files, format the memory
> card using fastboot recorded it all on the card. And received an error.
> I I had no prebuild files.
> are binaries for pandaboard. Could you please spend some time to flash > them on SD card, then confirm whether these works/does not work.
> (if these binaries won't work on your board, I'd ask you to download and > run validation image, to check if your board is not broken)
> Thanks!
> This is a complete system, I needed a custom system.I will be add my
application in this system. conclusion - I can't use completed system.
I tested my system on the other pandaboard and HyperTerminal gives me the same thing.A Pandaboard all is normal.
На русском: Мне нужна кастомная система, в неё мы будем зашивать свои приложения.Тестил 2ю борду с ней тож самое.
Calm down :) I understand your reasons, but:
1. have you followed exactly the steps to build the kernel?
a) apply the correct patches (please refer to the section Patching KERNEL)
b) use the correct toolchain (arm-2010q1, available from CodeSourcery, errr, MentorGraphics web site -- say, here -> http://www.codesourcery.com/sgpp/lite/arm/portal/release324)
c) use the default .config file, if you have made any changes to it (please find it attached)
2. if your system boots up to the login prompt, but you do not see nice picture on the display, it seems reasonable to provide the output of "logcat". Before reporting that "nothing works", make sure that you compiled and installed the SGX drivers as referred in the release notes.
3. And finally, if nothing else helps and even if you absolutely sure that you built all things correctly, try to use prebuilt images. If even them fail... probably, both your boards are broken. But I just finished rebuild this release, and verified it on all pandas that I have.
I am very sorry if I could not help you immediately.
I also hope that my english is understandable.
On 09/26/2012 01:57 PM, scherbakov...@gmail.com wrote:
> are binaries for pandaboard. Could you please spend some time to flash
> them on SD card, then confirm whether these works/does not work.
> (if these binaries won't work on your board, I'd ask you to download
> and
> run validation image, to check if your board is not broken)
> Thanks!
> This is a complete system, I needed a custom system.I will be add my
> application in this system. conclusion - I can't use completed system.
> I tested my system on the other pandaboard and HyperTerminal gives me
> the same thing.A Pandaboard all is normal.
> На русском: Мне нужна кастомная система, в неё мы будем зашивать свои
> приложения.Тестил 2ю борду с ней тож самое.