Re: Calypso Image

[Nikos Balkanas]

Oops. Sorry, I didn't realize that.
I will try to sort it out myself..
There aren't many names for this hook to have;-)
loadsystem, loadinclude...
If you remember anything about its name, plz tell me.

BR,
Nikos



On Thu, May 24, 2018 at 3:05 PM, Sylvain Munaut <246...@gmail.com> wrote:

> Hi,
>
> Sorry, as I said in my message, I don't have the patch and I don't
> remember anything about it ... It was 7 years ago ...
> And again, as I said in my previous message, search or ask in the
> hex-rays forum.
>
> Cheers,
>
> Sylvain
>

Re: Calypso Image

[Nikos Balkanas]

Hi Sylvain,

So, you are the author of the README and the web page, who did all the work
with Calypso.:)
I feel more comfortable working with C/C++ than Python.
The patch you couldn't publish 'cause of  Hex-Rays copyrights.
In the case of the hook, in what file should it be placed?
Calling convention?
In C++ it should create the same IDA structs as in Python.
Where can I find their description?
I'm using IDA + SDK 6.6.

Thank you,
Nikos
​

On Tue, May 22, 2018 at 8:17 AM, Sylvain Munaut <246...@gmail.com> wrote:

> Hi,
>
>
> > According to target_dsp/ida/README.txt, which is not signed, some of the
> > modifications to the Hex-Rays IDA SDK need the
> > author's help. I have compiled the processor with most of its attributes,
> > but I could use help with the stub feature to load include files.
>
> I don't have the patch any more, I wrote it for IDA 5.5 and most of it
> actually got merged by hexrays into mainline for 6.0, but not the type
> system.
> I actually didn't write support for it really ... just added a hook
> that did nothing and that allowed to load the .h once and then the
> patch wasn't needed.
>
> I did a post in the hex-rays forum asking how the type system worked,
> search
> for it, and I just implemented the hooks with default return values.
>
> The other option (which might be easier given it's really simple
> struct) is to convert the .h with a python script to IDC/IDAPython
> commands to
> create the 'struct' in IDA.
>
>
> Cheers,
>
> Sylvain
>

Re: Calypso Image

[Nikos Balkanas]

Any news?

According to target_dsp/ida/​README.txt, which is not signed, some of the
modifications to the Hex-Rays IDA SDK need the
author's help. I have compiled the processor with most of its attributes,
but I could use help with the stub feature to load include files.
Who is he and how can I get in touch with him?

TIA
Nikos

On Thu, May 17, 2018 at 11:09 AM, Nikos Balkanas <nbalka...@gmail.com>
wrote:

> Hi,
>
> I've downloaded Calypso's image. I would like to study it.
> Who did the analysis and what tools did he used for it in
> http://osmocom.org/projects/baseband/wiki/HardwareCalypsoDSP?
>
> TIA
> Nikos
>

Calypso Image

[Nikos Balkanas]

Hi,

I've downloaded Calypso's image. I would like to study it.
Who did the analysis and what tools did he used for it in
http://osmocom.org/projects/baseband/wiki/HardwareCalypsoDSP?

TIA
Nikos

Re: osmocom-bb compilation problems

[Nikos Balkanas]

OK. Finally figured out what I was doing wrong.
Did the Tip & Trick "Fetch fast from git.osmocom.org push to gerrit" and
thought adding gerrit to an existing clone was redundant and maybe
damaging:(
So, I omitted it and proceeded to push for review. Failed.
This time I added gerrit to an existing clone and proceeded with the push
for review:
-> git push gerrit HEAD:refs/for/master/Minor_Typo_Fixes
Counting objects: 32, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 96.41 KiB | 0 bytes/s, done.
Total 7 (delta 4), reused 0 (delta 0)
remote: Resolving deltas: 100% (4/4)
remote: Processing changes: new: 1, done
remote:
remote: New Changes:
remote:   https://gerrit.osmocom.org/#/c/osmocom-bb/+/9209 Minor Typo Fixes
remote:
To ssh://nbalka...@gerrit.osmocom.org:29418/osmocom-bb.git
 * [new branch]  HEAD -> refs/for/master/Minor_Typo_Fixes

I even got a mail alert from it
Finally it's over:)

Suggestion to avoid similar future issues:
Delete header "Add gerrit to an existing clone" and maybe add it as a
comment
Place Its content under "Push to Review"
Keeping it as a separate heading, made me think that It's unrelated to
"Push to review"
The choice of target "gerrit" in the push command is unfortunate, since it
can be confused for a host, gerrit.osmocom.org

BR
Nikos




On Thu, May 17, 2018 at 4:14 AM, Nikos Balkanas <nbalka...@gmail.com> wrote:

> Yeah, I have done all that.
> I'm still confused with the "Push for review" section.
>
> ->  git push gerrit HEAD:refs/for/master
> fatal: 'gerrit' does not appear to be a git repository
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> As I mentioned to Domi, I just need push priviledges to gerrit.
> This is my output:
>
> -> cat .ssh/config
> ServerAliveInterval = 300
> Host osmo
> Hostname gerrit.osmocom.org
> Port 29418
> User nbalkanas
>
> -> git push ssh://osmo/osmocom-bb.git
> Counting objects: 32, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (7/7), done.
> Writing objects: 100% (7/7), 96.37 KiB | 0 bytes/s, done.
> Total 7 (delta 4), reused 0 (delta 0)
> remote: Resolving deltas: 100% (4/4)
> remote: Branch refs/heads/master:
> remote: You are not allowed to perform this operation.
> remote: To push into this reference you need 'Push' rights.
> remote: User: nbalkanas
> remote: Please read the documentation and contact an administrator
> remote: if you feel the configuration is incorrect
> remote: Processing changes: refs: 1, done
> To ssh://osmo/osmocom-bb.git
>  ! [remote rejected] master -> master (prohibited by Gerrit: ref update
> access denied)
> error: failed to push some refs to 'ssh://osmo/osmocom-bb.git'
>
> gerrit is not a repository:( I also don't have priviledges to post to
> gerrit, which is fine, it is the gerrit
> master, and not the gerrit review...
> Not that for the git push output i've posted, all pubkeys and accounts are
> in order...
>
> Nikos
>
> On Thu, May 17, 2018 at 3:55 AM, Neels Hofmeyr <nhofm...@sysmocom.de>
> wrote:
>
>> On Thu, May 17, 2018 at 12:59:55AM +0300, Nikos Balkanas wrote:
>> > -> git push ssh://osmo/osmocom-bb.git
>>
>> Admitted, the patch pushing instructions only matched the case where one
>> added
>> a secondary 'gerrit' remote. So I tweaked the "Push for review" section:
>> https://osmocom.org/projects/cellular-infrastructure/wiki/Ge
>> rrit#Push-for-review
>>
>> In another mail you posted an SSH access error. You have added your SSH
>> public
>> key to your gerrit user as instructed on the wiki, right?
>>
>> ~N
>>
>
>

Re: osmocom-bb compilation problems

[Nikos Balkanas]

On Wed, May 16, 2018 at 3:38 PM, Neels Hofmeyr <nhofm...@sysmocom.de> wrote:

> On Wed, May 16, 2018 at 04:47:32AM +0300, Nikos Balkanas wrote:
> > ​I think I got it working. I got this cryptic response:
> >
> > -> git push ssh://osmo/osmocom-bb.git
> > Everything up-to-date
>
> That is definitely not how to push a patch for review to gerrit.
>
> Look, you're the first to have trouble reading the wiki page on Gerrit
> submissions, I believe the information there is quite clear. If it isn't,
> then
> we should fix that. Let us know where we lose you.
>

​Too much Information. Confusing.
There should be only 3 headers aside from the introductory why you use
gerrit:
1) Creating user in gerrit
2) Setting up gerrit for commits and pushing
3) Push Patch for Review

The only relevant entry in there is "Push for Review", and It is wrong:(

git push gerrit HEAD:refs/for/master/my_topic

It is different from what you told me in this mail, and gerrit is not an FQD.

When I try to use FQD for gerrit, I get pubkey errors:

-> git push nbalka...@gerrit.osmocom.org:29418
HEAD:refs/for/master/Minor_Typo_Fixes
Permission denied (publickey).
fatal: Could not read from remote repository.

If you still can't get it to work, please show us your ~/.ssh/config that
> you
> apparently use, share the state your git clone is in and your complete
> commandline and output that you use to push the patch.
>
> -
​> cat .ssh/config

ServerAliveInterval = 300
Host osmo
Hostname gerrit.osmocom.org
Port 29418
User nbalkanas

​-> git status

​On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git checkout -- ..." to discard changes in working directory)

modified:   src/README.building

no changes added to commit (use "git add" and/or "git commit -a")

-> git add src/README.building
-> git add -f src/shared/libosmocore/configure
-> git push ssh://osmo/osmocom-bb.git

Everything up-to-date



> ​Anyway to check if changes committed?
> > Cloning from gerrit will just give me ​the main osmocom-bb.git :(
>
> You are merely allowed to push a patch for review. Cloning osmocom-bb.git
> will
> only contain your patch if we approved and merged it. Usually that takes a
> couple of review iterations on gerrit.osmocom.org first.
>
> ​
That's a major shortcoming. CVS has its problems but at least you can check
what you have just commited:(​


> You have created a user on gerrit.osmocom.org?
>

​Yes, I created user and added public key. Otherwise I would keep getting:

Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


> ~N
>

Re: osmocom-bb compilation problems

[Nikos Balkanas]

On Tue, May 15, 2018 at 3:38 PM, Neels Hofmeyr <nhofm...@sysmocom.de> wrote:

> On Mon, May 14, 2018 at 09:38:42PM +0300, Nikos Balkanas wrote:
> > On Mon, May 14, 2018 at 8:12 PM, Nikos Balkanas <nbalka...@gmail.com>
> wrote:
> >
> > > Got it. I'm on it:)
> > >
> >
> > ​Tried to submit patch to gerrit:
> >
> > -> git push git://gerrit.osmocom.org/osmocom-bb
> > HEAD:refs/for/master/Minor_Typo_Fixes
> > fatal: remote error: access denied or repository not exported:
> /osmocom-bb
>
> Well, what can I say. Please carefully read the wiki page:
> https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
> you will note the URL ssh://$USERNAME@gerrit.osmocom
> .org:29418/$PROJECT.git
>
> ~N
>

​I think I got it working. I got this cryptic response:

-> git push ssh://osmo/osmocom-bb.git
Everything up-to-date

​Anyway to check if changes committed?
Cloning from gerrit will just give me ​the main osmocom-bb.git :(

Nikos

Re: Osmocon

[Nikos Balkanas]

Hi Domi,

You don't understand. I'm neither afraid or enthusiastic about it.
I cannot test yet. Still waiting on my phone:(

Nikos

On Tue, May 15, 2018 at 11:26 AM, Tomcsányi, Domonkos <d...@tomcsanyi.net>
wrote:

> Hi Nikos,
>
> I’m really happy to see someone being so enthusiastic about testing out
> OsmocomBB. It is definitely one of the most intereting open-source projects
> out there.
>
> However I feel like there is an imbalance between the amount of mails
> being sent and the amount of fiddling done. Don’t take this the wrong way,
> but if you attempted to compile the code and test it out, or watch some
> talks/videos you would not need to search for osmocon or try to extend it
> with USB support. I am only saying this because the amount of time spent on
> writing the mails in question would have been enough, in my opinion, to
> actually do the task in question. Therefore it does not always make sense
> to write an email before just trying it out. Don’t worry about trying out
> things, there is not much chance of you breaking anything :).
> All in all this software was created, as far as I know by people testing
> and trying tirelessly and eventually succeeding in achieving their goals.
> This is the spirit of hacking and open-source.
>
> Happy hacking, get your fingers dirty :)!
>
> Domi
>
>
> 2018. máj. 15. dátummal, 6:22 időpontban Nikos Balkanas <
> nbalka...@gmail.com> írta:
>
>
> I guess, both are serial protocols and the hardware adaptor takes care of
> legit default serial values.
> Still the problem is to find a free available usb port for communication:(
> Will have to test and see:)
>
>
> Nikos
>
> On Tue, May 15, 2018 at 7:02 AM, Nikos Balkanas <nbalka...@gmail.com>
> wrote:
>
>> Ty Craig,
>>
>> I'll try it for myself before changing anything:)
>>
>> I'm surprised, however, that osmocon can work like that. RS232 interfaces
>> need different initialization (baud rate, stop bits, parity, etc) that usb
>> doesn't understant!
>>
>> Nikos
>>
>> On Tue, May 15, 2018 at 5:24 AM, Craig Comstock <
>> cr...@unreasonablefarm.org> wrote:
>>
>>> Hi Nikos,
>>>
>>> > Planning to add usb support to osmocon.
>>> > Is there any interest for a patch, or should I do it just for myself?
>>> >
>>> > PS: You can convert a USB port to serial with a USB2serial converter:)
>>>
>>> Exactly. I have mostly used a USB to serial adapter without modifying
>>> osmocom-bb code at all. At one point I also built osmocom-bb natively on a
>>> raspberry-pi and was able to operate that way to some extent.
>>>
>>> -Craig
>>>
>>
>>
>

Re: Osmocon

[Nikos Balkanas]

Ty Craig,

I'll try it for myself before changing anything:)

I'm surprised, however, that osmocon can work like that. RS232 interfaces
need different initialization (baud rate, stop bits, parity, etc) that usb
doesn't understant!

Nikos

On Tue, May 15, 2018 at 5:24 AM, Craig Comstock 
wrote:

> Hi Nikos,
>
> > Planning to add usb support to osmocon.
> > Is there any interest for a patch, or should I do it just for myself?
> >
> > PS: You can convert a USB port to serial with a USB2serial converter:)
>
> Exactly. I have mostly used a USB to serial adapter without modifying
> osmocom-bb code at all. At one point I also built osmocom-bb natively on a
> raspberry-pi and was able to operate that way to some extent.
>
> -Craig
>

Re: Osmocon

[Nikos Balkanas]

Ty Vasil,

Found it:)

Seems it supports only serial interfaces:(
PCs since 5 years back don't have any more serial interfaces. Only usb:(
Planning to add usb support to osmocon.
Is there any interest for a patch, or should I do it just for myself?

PS: You can convert a USB port to serial with a USB2serial converter:)

BR
Nikos



On Tue, May 15, 2018 at 3:46 AM, Vasil Velichkov <vvvelich...@gmail.com>
wrote:

> Hi Nikos,
> На 15.05.2018 в 03:31, Nikos Balkanas написа:
>
> To run osmocom-bb I need to install and use osmocon.
> Can't find it in git repos. Where is it hiding?
>
>
> It's part of osmocom-bb. http://git.osmocom.org/osmocom-bb/tree/src/host/
> osmocon
>
> Vasil
>

Osmocon

[Nikos Balkanas]

Hi,

To run osmocom-bb I need to install and use osmocon.
Can't find it in git repos. Where is it hiding?

TIA
Nikos

Re: osmocom-bb compilation problems

[Nikos Balkanas]

On Mon, May 14, 2018 at 8:12 PM, Nikos Balkanas <nbalka...@gmail.com> wrote:

> Got it. I'm on it:)
>

​Tried to submit patch to gerrit:

-> git push git://gerrit.osmocom.org/osmocom-bb
HEAD:refs/for/master/Minor_Typo_Fixes
fatal: remote error: access denied or repository not exported: /osmocom-bb

Is the path right?​



> On Mon, May 14, 2018 at 2:45 PM, Neels Hofmeyr <nhofm...@sysmocom.de>
> wrote:
>
>> On Sun, May 13, 2018 at 09:28:57PM +0300, Nikos Balkanas wrote:
>> > The wiki is a non standard unix location, but a more convenient one. I
>> > propose to fix the info in README.building,
>> > to avoid future issues. The fix can be as simple as "Prerequisite is the
>> > armel toolchain. Check the  for installation"
>>
>> Patches welcome!
>> osmocom-bb is managed at gerrit.osmocom.org, to post a patch see
>> https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
>>
>> ~N
>>
>>
>

Re: osmocom-bb compilation problems

[Nikos Balkanas]

Got it. I'm on it:)

On Mon, May 14, 2018 at 2:45 PM, Neels Hofmeyr <nhofm...@sysmocom.de> wrote:

> On Sun, May 13, 2018 at 09:28:57PM +0300, Nikos Balkanas wrote:
> > The wiki is a non standard unix location, but a more convenient one. I
> > propose to fix the info in README.building,
> > to avoid future issues. The fix can be as simple as "Prerequisite is the
> > armel toolchain. Check the  for installation"
>
> Patches welcome!
> osmocom-bb is managed at gerrit.osmocom.org, to post a patch see
> https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
>
> ~N
>
>

Re: osmocom-bb installation problems

[Nikos Balkanas]

On Mon, May 14, 2018 at 2:29 PM, Neels Hofmeyr <nhofm...@sysmocom.de> wrote:

> On Sat, May 12, 2018 at 11:35:51AM +0300, Nikos Balkanas wrote:
> > Dear Harald,
> >
> > It was already pointed out to me, by Craig, that I was using the wrong
> > list:(​
> > I was using this list, because osmocom-bb configure told me so, in each
> > warning:(
>
> Hmm, might be worth a patch.
>

​I will be happy to submit one, if you tell me how to do it.​


>
> > Already have moved thread to baseband-devel.
> > I arrived at this conclusion probably because git clone libosmocore
> (master
> > branch),
> > gives me libosmovty 0.9.0.16:(
> > Will check out your link.
>
> If you are building from source: the git tagged version is put in a file
> called
> .version. Sometimes I needed to remove that manually and start from scratch
> (autoreconf -fi; configure) to get a newer version. Maybe that helps?
>

​Hmmm. I don't think it is a versioning problem.
The https request is ~6 mos old.
The git request is upto date.
Seems like caching from the nginx web server.
Solved my problem by using the git request:)
​


>
> ~N
>
>

Re: osmocom-bb compilation problems

[Nikos Balkanas]

Hi Sylvain,

I didn't realize it when you responded, but  is a toolchain
problem, and you just nailed it.
Cool:)

Early on, before it was pointed to me to use the Getting Started wiki, I
used the src/README.building file,
which is a normal practice for all unix developers/admins. When I couldn't
find the gnuarm.com toolchain, I searched the web
for ubuntu toolchains and found the linaro one, gcc-arm-linux-gnueabi,
which doesn't provide .
No dev version either:(
So, when using that toolchain, I had to come up with the missing
, and the only one I could find
was from vivado:(

Is there a point to my life's story? Just to pont out into how much
problems one can get with the wrong README file.
I realize that building procedure must be defined and maintained in 1
place, either the wiki or the README file.
The wiki is a non standard unix location, but a more convenient one. I
propose to fix the info in README.building,
to avoid future issues. The fix can be as simple as "Prerequisite is the
armel toolchain. Check the  for installation"

HTH
Nikos

On Sun, May 13, 2018 at 12:11 PM, Nikos Balkanas <nbalka...@gmail.com>
wrote:

> Thx Sylvain,
>
> For your fast response.
> This turned out not to be the problem, since I did several times make
> clean & make distclean, after I created the toolchain, before posting:)
> But your response helped, in that this isn't a usual problem. Therefore
> smt in my setup.
>
> Turned out problem was in my CPPFLAGS include dir.
> Early on, I faced a few problems with missing include files. 1 in
> particular  was nowhere in my system other than in Xilinx
> vivado,
> under /gcc-arm-none-eabi/.
> Once I removed it from CPPFLAGS osmocom-bb compiled fine (with a few
> warnings)
>
> Problem solved:)
>
>
> On Sun, May 13, 2018 at 10:15 AM, Sylvain Munaut <246...@gmail.com> wrote:
>
>> > I've been following the installation directions from the wiki, Getting
>> > Started.
>> > After generating the arm-none-eabi toolchain, I proceeded with make.
>>
>> My guess is you first tried compiling without an arm toolchain
>> installed and then installed the arm toolchain and didn't do a 'make
>> clean' when retrying.
>>
>>
>> Cheers,
>>
>>Sylvain
>>
>
>

Re: osmocom-bb compilation problems

[Nikos Balkanas]

Thx Sylvain,

For your fast response.
This turned out not to be the problem, since I did several times make clean
& make distclean, after I created the toolchain, before posting:)
But your response helped, in that this isn't a usual problem. Therefore smt
in my setup.

Turned out problem was in my CPPFLAGS include dir.
Early on, I faced a few problems with missing include files. 1 in
particular  was nowhere in my system other than in Xilinx
vivado,
under /gcc-arm-none-eabi/.
Once I removed it from CPPFLAGS osmocom-bb compiled fine (with a few
warnings)

Problem solved:)


On Sun, May 13, 2018 at 10:15 AM, Sylvain Munaut <246...@gmail.com> wrote:

> > I've been following the installation directions from the wiki, Getting
> > Started.
> > After generating the arm-none-eabi toolchain, I proceeded with make.
>
> My guess is you first tried compiling without an arm toolchain
> installed and then installed the arm toolchain and didn't do a 'make
> clean' when retrying.
>
>
> Cheers,
>
>Sylvain
>

Re: osmocom-bb installation help

[Nikos Balkanas]

Hi,

osmocom-bb configure gives me several warnings like this:

configure: WARNING: execinfo.h: present but cannot be compiled
configure: WARNING: execinfo.h: check for missing prerequisite headers?
configure: WARNING: execinfo.h: see the Autoconf documentation
configure: WARNING: execinfo.h: section "Present But Cannot Be Compiled"
configure: WARNING: execinfo.h: proceeding with the compiler's result
configure: WARNING: ##  ##
configure: WARNING: ## Report this to open...@lists.osmocom.org ##
configure: WARNING: ##  ##

Probably left out from a shared libosmocore configure, in
osmocom-bb/src/shared/libosmocore/configure.
That's how I used the wrong list:(

I tried the link: https://git.osmocom.org/libosmocore. Clearly shows latest
libosmocore tag is 0.11.0.
Interesting, when I try:
git clone https://git.osmocom.org/libosmocore
gives me libosmocore 0.9.0.16
git clone git://git.osmocom.org/libosmocore
gives me the correct libosmocore 0.11.0.12.
Seems your nginx server is caching the https request some 6 months now:)
Problem solved:)

TIA
Nikos

On Sat, May 12, 2018 at 4:09 AM, Nikos Balkanas <nbalka...@gmail.com> wrote:

> Hi,
>
> I am new to this list.
> I use ubuntu 14.04.02. I am trying to configure/compile latest master
> osmocom-bb.
> I ran into a few problems/questions:
> According to the src/README.building file, I should get the arm toolchain
> from gnuarm.com
> This should be updated, gnuarm.com doesn't have any downloads any more.
> Instead I installed gcc-arm-linux-gnueabi from ubuntu reps
> 1) normal gcc seems to support x-compiling for arm CPUs. Why not use that?
> 2) Your stock Makefile tests for CROSS_HOST against arm-elf-gcc. This
> should be updated to test also against arm-linux-gnueabi-gcc from
> gcc-arm-linux-gnueabi package
> 3) configure warnings:
> configure: WARNING: unrecognized options: --disable-tests,
> --disable-tests. Should be disabled if not supported any more
> checking for arm-linux-gnueabi-mt... no
> checking for mt... mt
> configure: WARNING: using cross tools not prefixed with host triplet
> Is there a problem to use the OS mt?
> 4) configure asks for libosmovty >= 0.10.0. libosmovty is part of
> libosmocore. Latest libosmocore master provides libosmovty 0.9.0.16-abc4:(
> These 2 should really be synchronized. Where can I find suitable
> libosmocore to work with latest osmocom-bb, or latest osmocom-bb that works
> with latest libsomocore?
>
> TIA,
> Nikos
>