ODROID GO Advance cell phone

[mameise]

Hi together,

i already showed it in another topic but thought this is worth its own

I built a SIM800L module (incl speaker and mic) into the OGA. Thanks to the plenty of space inside the case it was pretty easy. In theorie i would have an Odroid Go Advance cell phone now But only in theorie

I have troubles talking to it.
It is connected to the UART2 CON3 port on the right side.
As image i use debian buster

Can someone help me how to talk to the port? I tried with minicom on address ttyFIQ0 (thanks to mad_ady i know the address ) but i do not get an answer. I also tried the 10pin connector (UART1) but was also not lucky there.

I would really appreciate any help to get a first „OK“ from the module after sending „AT“ to it Then i could work on an App to make calls etc. Would be really bad if hardware mods would be that easy but software impossible

Thanks so much and i hope we get that cell phone working

[mat203]

Hey, I would perform a simple loopback test at first. Connect RX and TX and type a character using Minicom (ensure flow control is off). If you are receiving the character you are sure that both RX and TX line are working correctly.
The next step would be to ensure the connection is correct (TX SIM module -> RX Odroid and vice-versa, all power pins / reset pin of the SIM module connected correctly ?), furthermore check the interface settings like baudrate, parity etc.

The UART on the external connector is ttyS1 by the way.

[mameise]

Hey, I would perform a simple loopback test at first. Connect RX and TX and type a character using Minicom (ensure flow control is off). If you are receiving the character you are sure that both RX and TX line are working correctly.
The next step would be to ensure the connection is correct (TX SIM module -> RX Odroid and vice-versa, all power pins / reset pin of the SIM module connected correctly ?), furthermore check the interface settings like baudrate, parity etc.

The UART on the external connector is ttyS1 by the way.

I tried connecting both (RX and TX) together on ttyS1 but still no answer after typing something…
I turned on local echo to see what i type but Nothing Comes back.

Connection to SIM800L itself should be correct. RX -> TX , TX -> RX , and + and -
As i was not sure where to connect the reset pin i left it out but the module should work without it also.

[mat203]

I tried connecting both (RX and TX) together on ttyS1 but still no answer after typing something…
I turned on local echo to see what i type but Nothing Comes back.

Have you ensured flow control is off in the serial line settings of Minicom ?

This does not relate to the basic issue of not being able to transmit and receive over the port, but please also ensure the IO voltage levels correspond. If you power the SIM module with 5V and the module uses this voltage for the IOs you should include level shifters (at least for the TX line to the OGA, you can use a simple voltage divider). With 3.3V this is not required.

[joy]

Hi @mameise,

To use UART2 as a common serial driver, you need to disable fiq-debugger node in DTB first, then activate uart2.
/dev/ttyFIQ0 is dedicated to debugger outputs from defined serial id.
https://github.com/rockchip-linux/docs/ ... ernel/UART

[example] uart2 as a common console device
https://wiki.odroid.com/odroid_go_advan ... q-debugger

So could you try /dev/ttyS2 after modifying DTB as mad_ady's guide?
viewtopic.php?f=193&t=38117#p286641
Or I will provide a test dtb if you want.
(I think we need to arrange a guide like mad_ady's guide to change dtb without kernel build....)

And about uart1, which value of baudrate are you using?

[mameise]

Hi @mameise,

To use UART2 as a common serial driver, you need to disable fiq-debugger node in DTB first, then activate uart2.
/dev/ttyFIQ0 is dedicated to debugger outputs from defined serial id.
https://github.com/rockchip-linux/docs/ ... ernel/UART

[example] uart2 as a common console device
https://wiki.odroid.com/odroid_go_advan ... q-debugger

So could you try /dev/ttyS2 after modifying DTB as mad_ady's guide?
viewtopic.php?f=193&t=38117#p286641
Or I will provide a test dtb if you want.
(I think we need to arrange a guide like mad_ady's guide to change dtb without kernel build....)

And about uart1, which value of baudrate are you using?

Hi joy,

thanks for your answer.
Unfortunatelly i am totally lost how to do the changes... I was able to change a value from disbled to okay thanks to mad_ady, but to change / add complete sections i do not know the needed
commands...

A test dtb could also be very helpful I think not much missing to get it to work. Just stupid me

For uart1 i tried 9600 and 115200 but SIM800L should be set to auto and accept all.

[AreaScout]

@mameise

I did a lot with GSM modules on the XU4 (viewtopic.php?f=147&t=33860) and like @mat203 told already you have to disable hardware/software flow control in minicom after you get the kernel with UART2 support to run

It's not hard to compile the kernel, you can do this on any non ARM Windows (WSL) or Ubuntu machine by just following this instruction https://wiki.odroid.com/odroid_go_advance/build_kernel

Code: Select all

    +-----------------------------------------------------------------------+
    | A -    Serial Device      : /dev/modem                                |
    | B - Lockfile Location     : /var/lock                                 |
    | C -   Callin Program      :                                           |
    | D -  Callout Program      :                                           |
    | E -    Bps/Par/Bits       : 115200 8N1                                |
    | F - Hardware Flow Control : No                                        |
    | G - Software Flow Control : No                                        |
    |                                                                       |
    |    Change which setting?                                              |
    +-----------------------------------------------------------------------+

RG

[joy]

Hi @mameise,
Please find an attachment, oga_uart2test_20200323.zip.
-> oga_uart2test_20200323/rk3326-odroidgo2-linux.dtb

There are only two modification in the test DTB file to use common UART2 with /dev/ttyS2.
- disable fiq-debugger using uart2
- enable common serial uart2

And please note that you need to delete console=/dev/ttyFIQ0 in boot.ini.

First backup your original rk3326-odroidgo2-linux.dtb in vfat folder of sd card
and replace it with a new one.

Code: Select all

root@goadvance:~# ls /dev/ttyFIQ*
ls: cannot access '/dev/ttyFIQ*': No such file or directory
root@goadvance:~# ls /dev/ttyS*
/dev/ttyS1  /dev/ttyS2

[mameise]

Hi @mameise,
Please find an attachment, oga_uart2test_20200323.zip.
-> oga_uart2test_20200323/rk3326-odroidgo2-linux.dtb

There are only two modification in the test DTB file to use common UART2 with /dev/ttyS2.
- disable fiq-debugger using uart2
- enable common serial uart2

And please note that you need to delete console=/dev/ttyFIQ0 in boot.ini.

First backup your original rk3326-odroidgo2-linux.dtb in vfat folder of sd card
and replace it with a new one.

Code: Select all

root@goadvance:~# ls /dev/ttyFIQ*
ls: cannot access '/dev/ttyFIQ*': No such file or directory
root@goadvance:~# ls /dev/ttyS*
/dev/ttyS1  /dev/ttyS2

WHOOOOOOOOOOO Thank you so much!!!!!
After taking your dtb file, changing Name to ttyS2 i now get the Long expected "OK" after entering "AT"
Now i can continue writing an App to do calls
Again, thank you so much for your help. I think i would have never been able to do this without the file.

Edit: Already made the first successful call from the Advance to my cell phone.

[joy]

WHOOOOOOOOOOO Thank you so much!!!!!
After taking your dtb file, changing Name to ttyS2 i now get the Long expected "OK" after entering "AT"
Now i can continue writing an App to do calls
Again, thank you so much for your help. I think i would have never been able to do this without the file.

Oh! It works!
So glad to hear it.
Thank you for sharing the status.

I look forward to good result of your project.

[mameise]

WHOOOOOOOOOOO Thank you so much!!!!!
After taking your dtb file, changing Name to ttyS2 i now get the Long expected "OK" after entering "AT"
Now i can continue writing an App to do calls
Again, thank you so much for your help. I think i would have never been able to do this without the file.

Oh! It works!
So glad to hear it.
Thank you for sharing the status.

I look forward to good result of your project.

Yes it works Really happy now.

Btw i found issue for ttyS1 not working: It was working for sure but this "flow Control" Thing was another issue… Now also on ttyS1 i get "OK" after "AT" if
SIM module is connected.

[joy]

Btw i found issue for ttyS1 not working: It was working for sure but this "flow Control" Thing was another issue… Now also on ttyS1 i get "OK" after "AT" if
SIM module is connected.

So now you can control it now on ttyS1 as well with flow control option which @AreaScout shared. Right?
Good to hear it.

[mameise]

Btw i found issue for ttyS1 not working: It was working for sure but this "flow Control" Thing was another issue… Now also on ttyS1 i get "OK" after "AT" if
SIM module is connected.

So now you can control it now on ttyS1 as well with flow control option which @AreaScout shared. Right?
Good to hear it.

Correct
I also already installed pyserial and did the first tests -> works like expected.

Thanks again to all for the help. I am super happy now

[mameise]

I have a first test app ready No nice UI but at least already working. I can enter a number and call it and then end the call. Just a start of course but more to come.

[mad_ady]

Aren't there ready-made call apps for Ubuntu touch, for example? Couldn't you use one of them?

[mameise]

Aren't there ready-made call apps for Ubuntu touch, for example? Couldn't you use one of them?

Maybe there are but as i am a complete beginner in coding i would Maybe have more Troubles adapting something existing to work with my components
instead of making it new And it is a good experience and Training for me.
I have now made a start page where i can choose between calls, sms, Settings, contacts and dosbox
It also has a Header that Shows the Provider Name colored based on Network Status and the current time is also there.
I plan to start this program on every System boot so it will overlay the Desktop and act as my phone menu. It should then also indicate
new sms and missed calls etc. And as i only use Dosbox with this Image the Dosbox entry is everything i Need from the System itself

[mameise]

Update on Progress:

I have now finished following functionality in my phone app:

-make call either by entering number or selecting from phonebook
-phonebook: create, read, delete
-sms: receive, send, delete
-Settings: ringtone volume, ringtone select, Speaker volume
-launch dosbox from menu

Incoming calls and sms are indicated and for Incoming call the phone number is shown and one can pick up or reject the call.

I will make some photos of the UI (written in python using tkinter) but it is still just Basic. As all is working now i will concentrate to
make the look and feel better But i am really happy how everything works out so far.

[mad_ady]

So, for calls - what are you using as microphone? Something in your gsm shield? And is audio routed to internal speaker/headphones?
I thought your gsm shield only spoke serial...

[rooted]

You can see the microphone by the speaker, not sure about the rest of your inquires @mad_ady

[mameise]

I installed a second Speaker next to the original one and a microphone next to the analog stick (the small black circle) to be able to call without the Need of a Headset.
Both, the Speaker and microphone are directly connected to the SIM800 board.

[mameise]

You can see the microphone by the speaker, not sure about the rest of your inquires @mad_ady

This is the second Speaker, not microphone The mic is way smaller (the black circle on the left side next to the analog stick.
As i use the Speaker with my ear close to it for calls the small size is more then enough. Even the ringing is hearable good enough.
Could be louder and when i have it in my pocket i will not hear it but i anyway want to check possibilities to let the Advance Speaker
ring when a call Comes in or an SMS. I am also thinking of Building a Vibration Motor into it

[mameise]

Here is a picture of the current menu. Will make some more later Still all work in progress.

[mameise]

Some more pictures. As you can see the main page and the dialer page are more or less finished. Rest still ugly

[mad_ady]

If it works, but it looks stupid, it's not stupid!
Great job!

[mameise]

If it works, but it looks stupid, it's not stupid!
Great job!

Thank you

[joy]

@mameise,
Wonderful!!!
Thank you for sharing your progress.

Is it available to switch [cell phone app] <--> [emulationstation] flexibly in one OS image? (cell phone app acting as background service)
so you can get calls during enjoying games?

[mameise]

@mameise,
Wonderful!!!
Thank you for sharing your progress.

Is it available to switch [cell phone app] <--> [emulationstation] flexibly in one OS image? (cell phone app acting as background service)
so you can get calls during enjoying games?

Thank you

Well in general it is just a python script that is launched. I use it with the DebianBuster Image at the moment. So yes, i start the "phone OS" (app) and launch
Dosbox within the app. So the app stays active in the background (Dosbox gets a subprocess) and should indicate incoming calls during playing. But this is part
to be tested still.
I was also thinking a different approach but this will be impossible for me to do
In general it should be possible to now implement emulators into the app or somehow integrate the app into Emulationstation so i could even use it in a more
game-able image. But this is way bejond my knowledge unfortunately.

[joy]

@mameise,
I'm not an expert of your field and I don't have much knowledge of the service structure,
so just ignore my comment.
Your output is already cool enough.
Please keep going on your progress.

[rob6118]

Just wanted to say cool project. I recently picked up a Pinephone but am a big fan of the Odroid H2+. Would love to see an update on where you've gotten since the last post!