BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - JuergenD

Pages: [1]
1
Discussion - EVE / BT81x disabling Audio PWM
« on: June 15, 2019, 03:05:54 PM »
Hello,
we would like to disable the Audio PWM pin of the BT81x completely. Normally this pin gives us a PWM Signal after initialization of the BT, which we would like to eliminate. We would like to see here a static Signal. Is there a possibility to disable Audio PWM? we saw that playing a 'mute' Sound should do the Job, but in the documentation I saw Sound '62', somewere else '60', somewhere else '0'.
What is correct? is this the only possibility playing 'mute' or is there another possibility to disable this e.g by configuring the GPIO?

Thanks

2
Discussion - EVE / Re: BT81x -- used ASTC-Format
« on: May 03, 2019, 08:13:48 AM »
Great, this is exactly what we need. Thank you

3
Discussion - EVE / Re: BT81x -- used ASTC-Format
« on: April 30, 2019, 11:26:42 AM »
Hello,

thank you for your quick reply.

Unfortunately we have to use the ARM ASTC Encoder because this encoding must necessarily run on a Linux machine which feeds the content to an embedded device (which contains the BT81x)

The idea is to take the format, generated by the ARM Encoder, load it to the target  and convert it on the target before we load it to the BT Flash.
Means we have to write a converter for it, basically the same which you did in the Asset manager.

It would be very helpful for us to have some more Information about this conversion from the output, generated by the ARM ASTC Encoder to the format used by the BRT (and generated by the EAB Tool. It would save us a lot of time.

Could you provide us a code snippets for this conversation of this part of Code to get the ARM ASTC Output running on the BT81x?
Or maybe some more information or example?

Appreciate your help, thanks in advance.

Juergen

4
Discussion - EVE / BT81x -- used ASTC-Format
« on: April 26, 2019, 04:10:24 PM »
Hello,
as I understood, the ASTC-Format is a standard  Format, which is also used for different other GPUs, e.g. Nvidia, Andriods .

Is it necessary to use the 'original' Asset builder to convert Pictures to the ASTC-Format, used for BT81x or is it also possible to use ASTC-Pictures, directly generated from 3rd Party Tools?

In other words: does the ASTC-Format, which is used for the BT81x meet the Standards or is this a kind of propriatary format for the BT81x?

I am asking because I generated a ASTC pic, (of Course with the right Resolution and Format Settings) with a different tool and the binary, generated with this tool,  looked completely different to the pic, which was converted with the asset Manager. Header info looked completely different. (and is not working as expected)

Thank you


   

5
Discussion - EVE / BT81x CustomFont using unicode
« on: March 06, 2019, 07:33:13 PM »
Hello,

we try to get the BT81x run with a font set, contained in the BT81x flash. We converted the font set with the asset tool, loaded the glyph to 4096 ff and the .xfont to G-Ram, put this to flash_fast. So far so good.

The font basically  works, but it does not show up all characters, although they are contained in the font set. (we talk about characters on the first byte, 0 - 0xFF).

A small test program, displaying characters between 0 to 255 (using CMD_TEXT) should show everything, containing in the font set which is mapped in this range.

But it it shows characters between 0 to 190 properly, above it  shows  wrong characters (which is in the font set but on a different mapping), some show up nothing and some cause a crash on the BT81x and needs a reset.(which are some extra characters used for German language)

Seems that the xfont file points to the wrong glyph,  or to no-where.

the source font set works under windows with all characters properly and seems to be correct. The font set is completely converted with the asset manager (without the .txt file)

Is this a known issue, maybe of your font conversion tool?

What can I do, need the German extra characters mapped to the 'correct' codes.


Has anybody tried getting a unicode font set in the complete range (we talk about 1 Byte, 0 to 0xFF) wit the right mapping to work with CMD_TEXT?  What can I do, did I miss something?

would really appreciate your help. Tried to contact your support per mail, unfortunately no response so far.

Juergen

Pages: [1]