The shortcut of "Board Support Pack". These are basicly the device-specific drivers for Microsoft Platform Builder, and they are required if, usually an OEM, wants to build a Windows CE-based operating system for a device.
I'm trying to determine exactly when the external memory gets accessed (whether its internal flash or an SD card I don't care). I have successfully built a kernel module with kprobes monitoring do_fork() children lifespan times and verified it with an adb dmesg, which wasn't trivial. But I'm having trouble finding the kernel routine that solely accesses external memory, or has a parameter depicting access to external memory. Any suggestions?
Sent from my Galaxy Nexus using Tapatalk 2
As far as I understood - you want to hook functions that are writing/reading data&commands to the SFR's of certain controller (SDHC in your case)
I'm not sure what's order of calling or full abstract of that in Linux. But on most of OS there should be hierarchy like this, in given order
1) filesystem tree (everything under /)
2) filesystem drivers (for eg. fat32, ext2, ext4)
3) device drivers - perhaps part of some HAL exposing read/write functions (some generic thing like "io_device")
4) device type drivers - still common for all linux distros, like kernel MMC/SDHC/HSMMC driver (AFAIR you can find it in /drivers/mmc/~, there are few folders)
5) cpu/platform specific drivers - in case of ARMLinux, let's say for S5PC110 (Samsung Hummingbird) there's part in arch/arm/mach-s5pv210/, part in arch/arm/plat-s5p (plat-samsung and plat-s3c aswell, depends on release/revision/implementation), and core - CPU specific part in /drivers/mmc/host/sdhci-s3c.c.
In OMAP2 CPUs I'd look for these in arch/arm/mach-omap2, plat-omap2 and drivers/mmc/host/sdhci-omap.c
Perhaps you want to hook it somewhere on level 4 or 5.
Consider searching through documentation directory of linux sources. And prepare for alot of grepping.
SDHCI controller SFR structure is usually mostly the same for all ARM SoCs so I think there was some file containing most of functions used for all of them.
Hi Folks,
Brand new to the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Cran0g said:
Hi Folks,
Brand new ot the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Click to expand...
Click to collapse
You might not have enough ram in your PC, try 512mb that's as low as you can go for 4.2
Sent from my Nexus 7 using xda app-developers app
IRX120 said:
You might not have enough ram in your PC, try 512mb that's as low as you can go for 4.2
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hello,
I''m new as well and have exactly the same scenario on installing Eclipse on win 7 64 bits and try to learn with a Nexus 7 tablet.
I've tried adding the parameter to set 512mb but I'm still have the same problem. what else can be the problem ?
Thanks for any feedback.
Cran0g said:
Hi Folks,
Brand new to the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Click to expand...
Click to collapse
Did you solve this issue ?. I have exactly the same problem you have and I couldn't find any answer yet.
Thanks.
nexusnino said:
Did you solve this issue ?. I have exactly the same problem you have and I couldn't find any answer yet.
Thanks.
Click to expand...
Click to collapse
There seems to be a bunch of things that the prior respondents never bothered mentioning
- What version of OS are you using on your PC? (also, 32-bit, or 64-bit?)
- How much RAM is in your PC?
- After you boot up your PC, and have a look with the Windows Task Manager, how much memory do you have in use with your PC sitting idle?
- What version of the Android Developement Tools do you have installed into Eclipse (v21.1 or above)?
- Does your processor have Intel/AMD Virtualization extension support?
- You are *not* attempting to run an emulator under an emulator (e.g. VirtualBox) are you?
- Which API Level and Device are you trying to run from the AVD?
I have a Win7 Pro x64 box, i5 quad-core uP w/ VT-X extensions, 4 GB RAM. When I create (for instance) an "API Level 17" Nexus 7 emulator, the AVD dialog complains:
Android Virtual Device Manager said:
On Windows, emulating RAM greater than 768M may fail depending on the system load. Try progressively smaller values of RAM if the emulator fails to launch
Click to expand...
Click to collapse
Now, the default settings for a Nexus7/API 17 AVD device are 1024 MB RAM (just as with the physical device). When I attempt to run this way, sure enough I get a message
Starting Android Emulator said:
...Failed to allocate memory: 8...
Click to expand...
Click to collapse
but when I edit that virtual machine to use 768 MB, it runs just fine.
Monitoring the physical memory in use:
Windows 7 Pro x64: ~1.0 GB
+ Eclipse (v3.6.2) + AVD : ~ 1.2 GB
+ 768 MB Emulator Running: ~1.7 GB.
I conclude that the "768 MB" limit is some strange interaction between the ADT and Windows - I routinely operate other VMs on my machine that use up to 2 GB of memory.
hope that helps.
bftb0 said:
There seems to be a bunch of things that the prior respondents never bothered mentioning
- What version of OS are you using on your PC? (also, 32-bit, or 64-bit?)
- How much RAM is in your PC?
- After you boot up your PC, and have a look with the Windows Task Manager, how much memory do you have in use with your PC sitting idle?
- What version of the Android Developement Tools do you have installed into Eclipse (v21.1 or above)?
- Does your processor have Intel/AMD Virtualization extension support?
- You are *not* attempting to run an emulator under an emulator (e.g. VirtualBox) are you?
- Which API Level and Device are you trying to run from the AVD?
I have a Win7 Pro x64 box, i5 quad-core uP w/ VT-X extensions, 4 GB RAM. When I create (for instance) an "API Level 17" Nexus 7 emulator, the AVD dialog complains:
Now, the default settings for a Nexus7/API 17 AVD device are 1024 MB RAM (just as with the physical device). When I attempt to run this way, sure enough I get a message
but when I edit that virtual machine to use 768 MB, it runs just fine.
Monitoring the physical memory in use:
Windows 7 Pro x64: ~1.0 GB
+ Eclipse (v3.6.2) + AVD : ~ 1.2 GB
+ 768 MB Emulator Running: ~1.7 GB.
I conclude that the "768 MB" limit is some strange interaction between the ADT and Windows - I routinely operate other VMs on my machine that use up to 2 GB of memory.
hope that helps.
Click to expand...
Click to collapse
=========================================
Thanks for the message; here are the answer to the questions you sent:
1- I have Windows 7 ( 64 bits)
2- 4 GB of Ram
3- When the computer just started and idle use 1.3Gb of Ram
4- I've installed ADT V 22.0.1 - 685705
5- I can't find how to check if the VT-x is enable or not
6- I don't use any kind of Virtual Machine on this computer
7- API level is set to 17, but not sure what you refer to Device or AVD
As an extra comment I have and Nexus 7 that is running 4.2.1, that eventually I would like to test the apps in there.
Thanks for your time and help.
nexusnino said:
=========================================
Thanks for the message; here are the answer to the questions you sent:
1- I have Windows 7 ( 64 bits)
2- 4 GB of Ram
3- When the computer just started and idle use 1.3Gb of Ram
4- I've installed ADT V 22.0.1 - 685705
5- I can't find how to check if the VT-x is enable or not
6- I don't use any kind of Virtual Machine on this computer
7- API level is set to 17, but not sure what you refer to Device or AVD
As an extra comment I have and Nexus 7 that is running 4.2.1, that eventually I would like to test the apps in there.
Thanks for your time and help.
Click to expand...
Click to collapse
@nexusnino
Your setup looks pretty close to mine. Win7/x64, 4 GB. Now that I think about it a little more, I'm not sure if the VT-X processor extensions matter for the emulator, as the Android emulator is an ARM instruction-set emulator, not a true x86 native instruction-set VM.
(In my case, I built my own machine; knowing that I was going to be using VMs a lot, I went through Intel's processor model comparison database and selected an processor model that supports the VM hardware extensions. Intel sells a lot of "i5", "i7" processor model variants. In your case, you would need to find out the exact processor model in your PC to figure out if it has Intel VT-X or AMD/V. But, as I mention above, I'm not certain it is relevant to the Android emulators).
In the AVD (Android Virtual Device) v21.1, when I select Nexus 7, it pre-populates the VM RAM/Heap settings. If I leave RAM at 1024 MB, I get the error 8 message. But if I adjust the VM RAM size downward (e.g. 768 MB), the VM starts correctly. I didn't try other values - the /!\ caution message seems to indicate that other values, possibly higher, might work.
I just updated my ADT (and eclipse plugins) to 22.0.
Same deal on v22.0 as on v21.0 - the emulator errors out (error:8) if I leave the RAM set to 1024, but if I drop it to 768, it starts up just fine.
see attachment image
What happens if you drop the RAM settings down?
bftb0 said:
@nexusnino
Your setup looks pretty close to mine. Win7/x64, 4 GB. Now that I think about it a little more, I'm not sure if the VT-X processor extensions matter for the emulator, as the Android emulator is an ARM instruction-set emulator, not a true x86 native instruction-set VM.
(In my case, I built my own machine; knowing that I was going to be using VMs a lot, I went through Intel's processor model comparison database and selected an processor model that supports the VM hardware extensions. Intel sells a lot of "i5", "i7" processor model variants. In your case, you would need to find out the exact processor model in your PC to figure out if it has Intel VT-X or AMD/V. But, as I mention above, I'm not certain it is relevant to the Android emulators).
In the AVD (Android Virtual Device) v21.1, when I select Nexus 7, it pre-populates the VM RAM/Heap settings. If I leave RAM at 1024 MB, I get the error 8 message. But if I adjust the VM RAM size downward (e.g. 768 MB), the VM starts correctly. I didn't try other values - the /!\ caution message seems to indicate that other values, possibly higher, might work.
I just updated my ADT (and eclipse plugins) to 22.0.
Same deal on v22.0 as on v21.0 - the emulator errors out (error:8) if I leave the RAM set to 1024, but if I drop it to 768, it starts up just fine.
see attachment image
What happens if you drop the RAM settings down?
Click to expand...
Click to collapse
Thanks very much for the very detail post; I've adjust to 768 and I can consistently run without getting the error back.
Much appreciate your time and help.
Paulo
My tab specification's are 1.2 GHz quad core processor and 1 GB ram, 16 GB internal ROM.
I want to run RHEL 5.0 X86 CLI I mean without any gui on my tab and so I followed the steps below
At first on windows I have installed qemu manager and after that I have created a virtual machine RHEL with processor option as Pentium 3 and ram option with 256 MB. The installation was successful and I am able to boot properly into it.
After that I have transferred the installation image to my tab. In order to run the virtual machine I have installed limbo qemu manager. I have selected the transferred image and specified the same options as above.
When I run the above virtual machine I am unable to boot into my system properly and I getting the following errors
kernel panic not syncing: kernel compiled for Pentium+ requires TSC feature.
general protection fault : fffa [#1]
Kindly suggest how to successfully run the above virtual machine on my tab.
Regards,
Rupesh.
help
any ideas how to run net hunter kali on lenovo ideatab a3000?
Hello everyone!
Nice news today.
Android-x86 4.4-r1 (KitKat-x86) 2014/08/08
The Android-x86.org is glad to announce the 4.4-r1 release to public. This is the first stable release Android-x86 4.4 (kitkat-x86).
Key Features
The 4.4-r1 release is based on the Android 4.4.2 (KitKat-MR1 release). We have fixed and added x86 specified code to let the system runs smoothly on x86 platforms, especially for tablets and netbooks. The key features contain
Integrate the ffmpeg as the stagefright-plugins to support much more multimedia files. Now we can play HD and full HD videos in apps.
Use the latest longterm stable kernel 3.10.52 with more drivers enabled. Most netbooks can run Android-x86 in the native resolution.
OpenGL ES hardware acceleration for AMD Radeon and Intel chipsets (PowerVR chips are NOT supported).
Enhance the installer to support upgrade from previous versions (since ics-x86). The text based GUI installer supports ext3/ext2/ntfs/fat32 filesystems.
KitKat style lanucher (Trebuchet).
Support Multi-touch, Wifi, Audio, Bluetooth, G-sensor and Camera.
Support Huawei 3G modem.
Simulate sdcard by internal storage.
External usb drive and sdcard are auto mounted to /storage/usbX on plugging. Support filesystem vfat/ntfs/exfat/ext4.
Support hybrid mode of iso images.
Multi-user support (max 8).
Support Ethernet (DHCP only).
Support 5-point touch calibration on some devices.
Support VM like Qemu and VMware.
Released File
We tried to create a universal image for most x86 platforms for the kitkat-x86 release. The plan is still in an experimental stage. Please report bugs to the android-x86 forum with detailed specs of your machine and error logs.
android-x86-4.4-r1.iso
sha1sum: dce96b2ff7e81cc7c2a884f6028f114ca3133c20
The iso file is hybrid format. That means you can dump the iso into a usb drive and get a bootable usb stick, like
$ dd if=android-x86-4.4-r1.iso of=/dev/sdX
where /dev/sdX is the device name of your usb drive.
Known issues
Suspend and resume may not work on some systems.
The installer can't format ext3 filesystem.
Origin: android-x86 .org/releases/releasenote-4-4-r1
Doesn't change a bit for us, it doesn't support the blob mess that is our medfield chip (no powervr, no audio)