yashsingh1/xdaforums huggingface dataset:
[Gen9, Gen10 General] mmaruska:
serial console on turbo/4460

Hello,

I'm trying to replicate your success on the turbo version, with 4460.

So you soldered on those TPs?

But that's not really relevant - since the "peripheral mode" is used here on the last source -- same as original boot mode - is it?

I have tried to get connection with UART3 through mUSB --- recompiled kernel. But somehow the text is garbled, as if shifted

by 64. i.e. writing in minicom on my pc "12", I receive "qr" on the tablet.

---------- Post added at 12:53 AM ---------- Previous post was at 12:45 AM ----------

Could you advice on how to do the search for 4460?

I was supposing the pcb to be similar and removed a resistor at the same position, yet, when the tablet

is turned on, my pc sees an "archos" usb device, rather than a TI; so no boot over USB.
[Gen9, Gen10 General] scholbert:
Hi mmaruska!

Cool!!

Go for it... the mainboard with the OMAP4460 should be identical.

Yupp that's what i did.

You'll need a 1.8V capable logic though.

It is relevant, because the boot order changes.

In stock mode 1st boot device will always be used. Internal boot ROM of OMAP controls this, depending on the bootmode pins.

Unless there's useful code in the first block of internal eMMC, you can not enter peripheral booting with the stock setup.

Take a look in the hardware reference and grab some information in chapter 27 how the chip is starting up.

Mmmh could be several things, but no idea (and time) right now what is wrong...

How could you see what you receive on the tablet?

First of all, yes the mainboard of the OMAP4460 variants should be the same as OMAP4430... and yes, i got an advice as well...

Basically you need a better understanding of the boot modes, so please read the manuals and do a little research in the web.

To understand the USB peripheral boot mode, please refer to omap4boot or similar projects.

Your PC still identifies your tablet as Archos because it normally starts up, even with the boot mode changed.

If you like to use the USB peripheral boot you need a counterpart to give a response to the first strings send by the OMAP CPU over the USB.

This is a special program running on your host before you attach the tablet and before you power up the device.

You'll need a low level driver for OMAP44xx on a Windows host as well.

So better use omap4boot on a Linux host and follow the wiki of that project to use USB booting.

Hope this helps!

Please keep me informed and good luck for your next adventure :fingers-crossed:

Regards,

scholbert
[Gen9, Gen10 General] -DMA-:
Hi guys! I have a RK2918 pad with EJ080NA-04B LCD onboard. I need to bulid a new kernel for fully support JB firmwares but can't find drivers for this display. This display don't need additional drivers and could be compiled with some config changes? At this moment I have a black screen with any kernel which I can find for RK2918 but stock kernel works fine. P.S. sorry for my english.
[Gen9, Gen10 General] trevd:
A bit random! :laugh: I'd check the lcd-backlight brightness through sysfs , it maybe just a case of turning the screen on... I also think your queries maybe better served on slatedroid http://www.slatedroid.com/topic/17531-rk-2918/

:good:
[Gen9, Gen10 General] -DMA-:
thank you for quick answer anyway :good:
[Gen9, Gen10 General] vicencb:
Status update

Hello!

I've been requested for a status update, well, here it is...

There are some news from the Barebox bootloader and also from the Linux kernel.

Barebox will soon have keyboard support (up, down and enter) and a menu.

If no keys are pressed the first kernel found from a predefined list will be booted, else a menu will show up (on the serial port :( ) and an entry could be selected with the available 3 keys.

The list of kernels to boot is 1) Linux kernel from sd-card 2) Android kernel from sd-card 3) and 4) the same but from usb

This list is still a work in progress...

Android?? Yes! Barebox can boot the factory default Android kernel!

From the Linux front little progress, only have this working:

uart was already working

sd-card and internal flash are accessible

wifi works

still to set up:

battery, display, touch, hdmi, audio, usb, gps, accelerometer, compass.

In summary: all that's not listed as already working.

In general Linux for ARM SoCs gives me the impression that's still a work in progress.

The ARM CPU is well supported, but every SoC is a world in it's own, each one with it's own set of peripherals, interconnected in different ways, ..., too much work.

For this reason when porting Linux to the tablet I'm using the most up to date Linux kernel, so all that is working does so on 3.8.2

Sometimes I've looked at some other variants (Linaro, the kernel from omapzoom and some others) but found more or less the same state of support, so I've keept with the vanilla version.

The DeviceTree looks promising, but it's still not fully supported for omap4.

If someone is interested in Barebox: check it out from the official web site when everything is upstreamed in some time.

If someone is interested in Linux: tell me and I'll post the patches.

Have a nice hacking,

vicencb
[Gen9, Gen10 General] Quallenauge:
Vincent!

That's great work!!!!

I have some questions to this:

Would it be possible to use this kernel without barebox, e.g. can the stock bootloader used to start this kernel, or does barebox setup some things before the kernel is loaded? I would like to try some things out, but I don't opened my device, so I have no access to the internal UART.

Without this, I can't get not so much (=none) kernel messages.... Would it possible for you to provide an kernel which sends his output to the UART3?

Thanks!
[Gen9, Gen10 General] Quallenauge:
Hi,

I soldered the serial pins and started with hacking =)

Currently I would like to make some progress with the 3.4 kernel from omapzoom. I get the (basic, omapfb driven display) and internal mmc running, and thats the current state. A the moment I try to get the musb running - it seems that all drivers loads fine on the tablet, but I don't see the device with lsub?

Also I have an (bigger) issue with the serial communication, which prevents to use kdb or kgdb :(

I get the kernel output from the serial line but I can't type - seems like I have an read-only mode !?

For example: When the kernel debugger starts it doesn't accept my typed commands in a minicom console (on my PC).

Also busybox isn't accepting my keyboard input.

I checked, that flow control is set to off on my PC. On the kernel side, I really don't know how to setup this special setup.

Has anyone an idea what's going wrong on this?
[Gen9, Gen10 General] Quallenauge:
Just an update:

If someone would like to start hacking and has an archos A80S 1GByte model, then

here you go linux-jb-3.4 .

Currently the ADB is working, so no need for serial console for basic hacking ;)

Sadly I can't get the serial line working correctly, so only output but no input back to the console is possible.

However, with the same hardware and same host configuration, it is possible to do this with the stock kernel....
[Gen9, Gen10 General] vicencb:
I've seen this post:

http://linuxgizmos.com/introducing-the-new-beaglebone-black-kernel/

which says:

This summer, we’ll be tapping the TI kernel development team and a number of interns to help the BeagleBoard.org community and key developers in cleaning up patches that aren’t yet submitted and pushing them to the upstream maintainers as well. We’ve skipped 3.9 and will be hopping back on the mainline train for the 3.11-rc.

I kind of gave up on this after trying several kernels:

.- with vanilla 3.8 achieved most, but the battery charger driver has thousands of dependencies and after trying porting all of them it still has not worked.

.- with omapzoom 3.4 battery charger works well, but other things doesn't work (eg. wifi)

Now I hope that the beagleboard team achieves this big milestone on 3.11 to try again.

There are several things you can try:

First of all, try your serial port with a software known to work. For example scholbert's u-boot or upstream barebox.

Barebox tries to boot without user interaction because not always the serial port is connected. So you have to have the volume-down button pressed while booting barebox. Then it will show you a menu on the serial line. When you see it try pressing the arrow keys to check the serial port.

If it works then the problem is a software issue with your kernel, else is a hardware issue.

In the first case ensure gps is disabled (gpio41 ==> 0) and 1v8 is powered-on (gpio34 ==> 1). Also check the UART3 MUX pins are correct. If your kernel does not modify this settings them should be the ones from the bootloader which has already been tested.

In the second case check your cabling with this:

http://xdaforums.com/attachment.php?attachmentid=1147573&d=1340370106

Also check that your serial adapter works at 1.8V when shorting rx and tx.

Regards,

vicencb.
[Gen9, Gen10 General] Quallenauge:
Hi Vicencb!

Thanks for your hints. I found that I had to disable the serial line in barebox configuration. After that I was able to type keys and use the debugger.

I'm getting warm with the 3.4 kernel. These things works:

Gyroscope

Accdelerator

Charging

Display

Touchscreen

Audio

Internal MMC Access

Bluetooth

Camera ("Forward ported" the remoteproc drivers to be compatible to the ducati binary). (Sometimes there must be a race condition...but thats okay for an alpha version).

In short, a basic android system comes up. Which is quite usable, BUT the missing wifi hurts (like you mentioned). I'm feeling that I'm nearly done but I don't have any glue how to get the wifi running. Everytime I would load the sdio driver a

91.168182] wl1271_sdio mmc2:0001:2: sdio read failed (-84)

is thrown, which must be solved first, to get up and running the device. An short log is here: http://pastebin.com/HAW66A6C. (As a side node, why is the module probed twice?).

As usual, my repo contains the current state: https://github.com/Quallenauge/kernel-archos/tree/linux-jb-3.4

Any ideas on that?

Can you please provide a patch for your kernel, maybe we have a chance to get a closer look on the differences between these kernels.

Maybe the hwmods where changing. Also maybe the hsmmc driver was updated.
[Gen9, Gen10 General] Quallenauge:
Instead of adding more and more debug statements, comparing the debugfs entries with stock and this one, modifying the stock kernel to get a glue what is going on, verifying the clock values and hwmod entries I should more think about the problem ;)

I found the solution:

In board-44xx-serial.c the standard uarts are initialized. Also uart4 which is used by the archos wifi device. So these values doesn't match! So I had to disable this (one) line and wifi sdio seems to work. :D:D:D

/*
* UART: Tablet platform initialization
*/

void __init omap4_board_serial_init(void)
{
...
//	omap_serial_init_port(&uart4_board_data, &uart4_info);
}

I didn't trying some more, I would now enjoy the nice weather and continue next days....

Edit: Can't wait to try it out ;) Wifi works now...changes are uploaded to github.

The HD video doesn't work yet... I will have a look on it....Hope this isn't a show stopper...
[Gen9, Gen10 General] scholbert:
Hey Quallenauge,

sorry for being little late :o

I read related posts again and remembered what i did once to activate early kernel messages on UART1 (testpoints) without the need of feature tags.

Have a look again at this old patchset i once created:

http://xdaforums.com/showpost.php?p=29995828&postcount=62

You'll need some additional things set up in the config and do little tweaks to the archos-fixup.c file to make it work.

... and if i remember correctly it might be required to override the default kernel cmdline as well.

Just step through the patch and you'll see.

Should be easy to adopt this for UART3 (alternate function of usb-otg pins).

Anyway great progress with your project. It's really amazing :victory:

Have fun,

scholbert
[Gen9, Gen10 General] Quallenauge:
Just a short note! I'm seeing my first HD video on the 3.4 kernel on youtube - YEAH!

I had some troubles to getting the dynamic ION to work, but now it seems tor work for the moment.

Not very clean code but it works - I think I don't really understand what I'm doing here ;)
[Gen9, Gen10 General] Quallenauge:
Just an update:

I looked at the changes of Archos and found that in file omap_hwmod_44xx_data.c the HWMOD_INIT_NO_IDLE | HWMOD_INIT_NO_RESET flags are removed.

static struct omap_hwmod omap44xx_uart3_hwmod = {
.name	= "uart3",
.class	= &omap44xx_uart_hwmod_class,
.clkdm_name	= "l4_per_clkdm",
[B]//	.flags	= HWMOD_INIT_NO_IDLE | HWMOD_INIT_NO_RESET,[/B]
.mpu_irqs	= omap44xx_uart3_irqs,
.sdma_reqs	= omap44xx_uart3_sdma_reqs,
.main_clk	= "uart3_fck",

.prcm = {
.omap4 = {
.clkctrl_offs = OMAP4_CM_L4PER_UART3_CLKCTRL_OFFSET,
.context_offs = OMAP4_RM_L4PER_UART3_CONTEXT_OFFSET,
.modulemode = MODULEMODE_SWCTRL,
},
},
.slaves	= omap44xx_uart3_slaves,
.slaves_cnt	= ARRAY_SIZE(omap44xx_uart3_slaves),
};

So I did the same and end up with the following log messages:

[ 71.249511] PM: suspend of devices complete after 205.688 msecs
[ 71.250152] PM: late suspend of devices complete after 0.610 msecs
[ 71.251525] omap_device: omapdss_dpi: omap_device not built
[ 71.252319] PM: noirq suspend of devices complete after 2.136 msecs
[ 71.252349] Disabling non-boot CPUs ...
[ 71.254333] CPU1: shutdown
[ 71.256683] Resume timer @65535.000Secs(2147450880 ticks @ 32768 Hz)
[ 71.256713] PD_CORE curr=ON prev=ON logic=ON
[ 71.256713] Powerdomain (core_pwrdm) didn't enter target state OSWR (achieved=ON current=ON saved=ON)
[ 71.256713] Could not enter target state in pm_suspend
[ 71.256713] At Resume: IRQ 39(TWL6030-PIH)(OMAP-IRQ=7) Pending! Wakeup Enable: CPU0=no,CPU1=no
[ 71.256713] At Resume: IRQ 40(unknown)(OMAP-IRQ=8) Pending! Wakeup Enable: CPU0=no,CPU1=no
[ 71.256713] At Resume pending I/O pad: Reg - 0x4A1001EC, CONTROL_PADCONF_WAKEUPEVENT_5[13]
[ 71.256713] Suspended for 27.508 seconds

One step closer =)

Maybe the PD_CORE is active because of my workaround to avoid shutdown the mailbox handle.

PS: When developing with barebox, some other powerdomains can't be shut down. As I read, this is normal that some bootloaders doesn't setup the power domains correctly.

People recommend to use the same bootloader with same git revisions (The embedded world is full of miracles :) ).
[Gen9, Gen10 General] Quallenauge:
Hi,

about the mailbox issue: I found a workaround

arch/arm/plat-omap/mailbox.c

I commented out the context restore skip logic:

static int omap_mbox_restore_ctx(struct device *dev, void *data)
{
struct omap_mbox *mbox = dev_get_drvdata(dev);

// /* mailbox is not init'ed.. no need to restore */
// if (!mbox->use_count){
// return 0;
// }

So with that code, the mailbox seems to go to sleep. But the core power domain is leaving in power on state...

Also I found out, that after a suspend, the ipu/remoteproc doesn't work anymore. :( Something is sleeping forever....
[Gen9, Gen10 General] unasoto:
just found this thread and its been a most enjoyable read. :) is there any progress or is it a dead project
[Gen9, Gen10 General] ledokol:
Help!

Help me please to define element Archos 80g9 8pin mark 5QAF.Operates display illumination. My is died. Than to replace?
[Gen9, Gen10 General] ledokol:
I have solved this question, it is MP3304ADD
[Gen9, Gen10 General] carefreeway:
1. Is it possible to upgrade 80 G9 Turbo version (with OMAP4460) RAM from 512 MB to 1 GB by unsoldering/soldering chip on the board?

2. Is it possible to upgrade touch screen to more decent one? My old one has broken. It has FPC-TP20524A-V1 -C 149 inscription on its board and 8CTMA340-48LQI-01 on the board's chip.

P.S. 8CTMA340-48LQI-01 means Cypress PSoC CMOS Multi-Touch All-Points Controller 48-Pin QFN, 0.6-mm Height 2 fingers max., 4.5" max screen size (Can support up to 7” diagonal with stretched sensor pitch), 252 nodes max, it also has bootloader, I2C and SPI interfaces.
[Gen9, Gen10 General] carefreeway:
Newer modifications of 80 G9 Turbo have different touchscreen and display subsystems:

Display subsystem

• ChiMei 8" TFT-Display EJ080NA-04C (24Bit-LVDS interface)

Touchscreen subsystem

• Capacitive touchscreen unit (Tango F48 PIX90048NQ chip with TR16C0 controller on one board).

The replacement of display is fully compatible, but the change from old to new touchscreen board won't be so easy.

P.S. If you need instructions on how to change your touchscreen from your original to another revision of the same A80S (or another) board just ask. I have done this not so easy procedure successfully.
[Gen9, Gen10 General] scholbert:
JTAG (untested yet!)

Hey there,

it's great to see some guys still play around with this ancient tablet :)

So... as requested by carefreeway via PM, here are the JTAG testpoints i traced a few years ago.

Just to mention it, i never used this interface, because the OMAP4430 offers a lot of other modes to play with.

This functionality is not confirmed to work or tested by me, but the assignment should be correct!

Anyway, have fun!

Cheers,

scholbert
[Gen9, Gen10 General] Rusik12:
Help me please change touchscreen
[Samsung Galaxy SL i9003] vijaypalmanit:
As we all know Flipboard is one of the best designed apps for news consumption - with plenty of visual flare, it makes it easy to spot important news and gives publications a magazine-like feel.

so If you want all those cool features in your mobile and don't want it to be launched in Market, we are here to help you with the extracted .apk
[Samsung Galaxy SL i9003] ghostcowboy:
Great men, it is very useful, but not working so well with mod roboto font ^_^
[Samsung Galaxy SL i9003] Leegalaxy:
Works great on my galaxysmtd running CM9 nightly.
[Samsung Galaxy SL i9003] vijaypalmanit:
The one thing which i like in this is the smoothnes..
[Samsung Galaxy SL i9003] vishal24387:
ya...but it doesnt have indian news.
[Samsung Galaxy SL i9003] ghostcowboy:
There is an new update but i couldn't download it, anyone does??
[Samsung Galaxy SL i9003] cxo:
Here's the updated version

http://db.tt/83xYp2VL
[Samsung Galaxy SL i9003] vijaypalmanit:
Yeah this new update is good..and fixed some issue too
[HTC One X] TwanVeugelers:
Hi.

I have setup my lockscreen to show the Productivity Screen.

My agenda is set up to only show my gmail agenda.

Still I only get Facebook notifications shown on lockscreen.

What am I doing wrong here?

grtz,

Twan
[HTC One X] TwanVeugelers:
nobody?? really??

yes, this is a bumperpost.
[HTC One X] steinerhippo:
Hi,

i am on 1.29 FW and the problem still exists. You can choose the calendars you want to see, but i think HTC forgets to check these settings when showing the entries on the screen.

I hope they fix this in a upcoming FW
[HTC One X] ghost-5:
I've only just started using this setting so I've not had any Facebook events appear yet but I noticed when you click on a calendar event it takes you to the HTC calendar app where it showed the Facebook calendar. I have unselected it in there and will see how I get on
[HTC One X] TwanVeugelers:
I have set up mycalendars to not show any Facebook events. It keeps puzzling me.

grtz, Twan
[HTC One X] jeyml:
I think is a bug,the only way you can remove the facebook calendar is to go into settings>accounts and remove the facebook account..
[HTC One X] TwanVeugelers:
I disabled the Facebook calendar sync (settings-accounts-facebook-calendarsync) can't check yet; as there are still some items today.... w'll see....

grtz, Twan
[HTC One X] TwanVeugelers:
neither the sw upgrade to 29.401.11 nor the setting mentioned in the previous post solves this.
[HTC One X] webpatrick:
You can swipe through your today calender items on the lockscreen (left + right).
[HTC One X] f_padia:
I have this problem too, is it definitely a bug? does anyone know if its fixed in any of the custom ROMs?
[HTC One X] Super Saiyan:
I've had this issue since day 1 on my HOX, its made me stop using the Productivity lockscreen unfortunately.

Hope its fixed soon
[HTC One X] Gulioth:
I've just noticed this too - very annoying! Is there no fix for this then and if not has anyone raised a case ticket with HTC?
[HTC One X] Gulioth:
Aha! Resolved. Go to Personalize > Lock Screen Style > Settings and at the bottom you can choose which calendars & subsequently their notifications appear on the locked screen.
[HTC One X] TwanVeugelers:
Hi Gulioth.

Have you actually read the reason for this topic?

The HOX just does not "disable" the FB calendar after you deselect it.

It keeps showing the FB calendar.
[HTC One X] Gulioth:
Yes thanks, understand the problem - the above solution worked for me & I no longer have FB notifications on the locked screen
[Windows Phone 7 Q&A, Help & Troubleshooting] unbenannt:
hello,

i have an omnia 7 and since a few days the m.youtube.com site does not work anymore. it opens the site, but there is no video to play (though it displays the video description and a sign where it says "video is loading"). then it redirects me to the desktop site (i think) but the screen stays white.

anyone has the same problem?
[Windows Phone 7 Q&A, Help & Troubleshooting] Localhorst86:
hm.. it works fine for me on my Mozart. I see the website, I see the video and if I click it, the youtube app opens and plays the file.
[Windows Phone 7 Q&A, Help & Troubleshooting] GoodDayToDie:
You could try using the HTML5 streaming - WP7 can play MP4 movies embedded in HTML5 <video> tags, and YouTube supports this - by going to http://youtube.com/html5 and opting in (on your phone). I usually use the desktop mode, which didn't launch in the (kind of lame) app anyhow.
[Windows Phone 7 Q&A, Help & Troubleshooting] dragoxt:
hi i had this issue before on the address bar try https://m.youtube.com in other words the secure HTTP "HTTPS" for one reason or another the HTTP dint work for me.
[Windows Phone 7 Q&A, Help & Troubleshooting] sjyoung12:
I had the same problem, and manually specifying the HTTPS protocol worked for me.
[Wildfire Q&A, Help & Troubleshooting] Euroxi2:
htc wildfire Touch screen not responding

My Smart phone is htc wildfire 2.2.1 A3333

S on , unroot , working 100% no Problem

-----------------------------------------------------------------------------------------------

[FULL GUIDE] Rooting HTC Wildfire (BUZZ) 2.2.1 with HBOOT 1.01.0002 !! (5/8/2011)

http://xdaforums.com/showthread.php?t=1145035

After

Step 1- create Gold card (Step 100% work)

Step 2- S Off (Step 100% work)

#Downgrading from Android 2.2.1 Froyo to Android 2.1 Eclair# In this Step 3 is Problem

Step 3- install RUU_Buzz_HTC_WWE_1.14.405.2_R_Radio_13.45.55.24_3.35.15.31_release_130814_signed

install done

Start my phone ,launch Android 2.1 Eclair

Problem

"Touch screen not responding or Touch screen Freeze" :confused::confused:

1- i can't enable USB Debugging

2- i can't launch clock work mod Because phone NotRoot

3- i can't insall RUU_Buzz_HTC_WWE_1.37.405.exe from bootloader error 140 connect (but Connected the phone to your computer via USB cable 100% work and show "Android bootloader interface" in computer) :eek:

I Need help
[Wildfire Q&A, Help & Troubleshooting] amNezic#:
Hi, i have the same problem after downgrading my 2.2 froyo to 2.1 eclair that rom it's not good! obviously it's freezing your touch screen after u turn on your phone.

Here it's the rom u need to downgrade to 2.1 (eclair) stock!

I also follow the same topic and needs to be corrected the link with rom 2.1 eclair

U have u tap http before the link below because i don't have permission to post external links before i have already 8 post on this forum. It's a bit annoying this rule.. ok fine! do what i tell u!

shipped-roms.com/download.php?category=android&model=Buzz&file=RUU_Buzz_HTC_WWE_1.25.405.1_Radio_13.45.55.24_3.35.15.31_release_142189_signed.exe

U just run it like the another one.. And things will just work fine ! Balls of steel :)