Skip to main content ↑ ↓

Messages

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

Messages - robots

49
Project development, ideas, and suggestions / Re: RDA1846 Transceiver Chip
If you look at the portfolio of the receivers/transmitters/transcievers they all look the same:
mixer outputting I/Q signal, DSP, and some output pins (GPIO). Transmitting part just backwards.
It's a "platform" created by silabs - like lego, just with signal processing blocks + the DSP that can be programmed. And the RDA1846 chip is based on the same platform, just the DSP firmware is created by the Chinese company.
50
Project development, ideas, and suggestions / Re: RDA1846 Transceiver Chip
That part of spectrum is useless here in EU :-), It is only available in IARU 2 to hams.

The experimenting would be nice, if one could access the raw I/Q data, or have the possibility to upload own SW into the built in DSP.

BTW: those chips are made by Silabs, or at least the technology is silabs' technology. If you look at:
http://www.silabs.com/products/audiovid ... fault.aspx
The block schematic looks pretty much the same as the RDAxxx chip.
51
Project development, ideas, and suggestions / Re: RDA1846 Transceiver Chip
Wouldn't it be easier and cheaper to hack the UV-3R radiostation and break-out the SPI/i2c interface from that chip ? It already contains all the filtering necessary, power amp, receive pre-amp, signal switches, etc etc, most of is controllable from the RDAxxx chip via GPIO.
52
Bus Blaster JTAG debugger / Re: Busblaster, openocd and the BeagleBoard xM
Be sure not to have the jumper on BBv2!!,  The BBv2 is powered from USB, and by shorting the jumper you will provide 3V to the JTAG target.
When the jumper is opened, target will provide the voltage to the "buffer". (Beagleboard is 1.8V, BBv2 can work with targets from 1.8 to 3V)

I am not sure about the EMUx pins. They are not necessary, but need to have in some state, for he openocd to work. (I think they can by controlled through the JTAG) You will need to make some more research about that :-)
54
Open Bench Logic Sniffer / Re: Rewrite of ols firmware
I had problems with modulo operator, because i copied the prototype of interrupt routine (with the pragma). The problem was the "nosave" of prod registers.

The trouble with USB stack was non working interrupts, this was related to not understanding how interrupts are handled in OLS. (there is a jump from bootloader to application, and requires special pragma on certain functions).

I would guess that interrupts are the problem. As this firmware will probably not work without interrupts.
55
OpenOCD JTAG / Re: BPv4 support
It seems that all the OOCD_*_OCD defines should have suffix *_ODC, like BP_CS_ODC, but I wonder where that suffix got lost :-) (it used to work some time ago)

Quote
I suggest using BP_AUX2 instead of BP_PGD for TRST signal, as now there is enough pins on the IO port.

Sure. I was just lazy :-)
56
OpenOCD JTAG / Re: BPv4 support
Openocd patch is already in works. I just didn't have enough time to test it properly :).

I am having trouble with output pins, as the TDI, TMS or TCK are missbehaving.

I have taken different approach. Receive the data as they come, and process them. If the buffer gets full, usb will stall host, so no lost data. (Probably a bit faster approach than buffering all, and transmitting.)

You also need to know that adding new functionality doesn't mean commenting out BPv3 functionality.

I have also extended the "Features" of the protocol (This is not yet patched in the OpenOCD):
- support for pullup source
- more ADC measurements (VUSB is added for BPv4)

I was aiming for a working C code, and then rewriting it into assembly.
59
Pirate PIC programmer / Major changes in the PicProgrammer
Hi,

First of all, if unsure use "r1816" version of the PiratePicProg, which works and doesn't need any new firmware in buspirate.

I have posted the most recent commit to the SVN. The current changes are:
- changed Interface api:
Read, Write commands are not returning anything, Get Data returns data. This way you don't have to wait for every single command to be completed. You can queue the commands and send them in bulk.
This also means new programing protocol in buspirate (see below)
TODO: change read/write function prototypes.

- changes to Pic24:
the programming is done according to datasheet, no relying on command side-effects.

-Added first PIC16:
added 16f88x family programming protocol. Tested with (ancient) High voltage programming adapter. Supported is read, write, erase, write fuses. (Write user ID is blocked now and should work fine)

-memory:
support for different word sizes (14, 16, 24 ...), also support for empty check on different word sizes.

-the new firmware:
New protocol has been added to the buspirate (also in SVN). Attached is compiled version that works, but the terminal interface has broken strings (binary mode works fine).

-future work:
add support for pic32
remove some divide by 2 multiply by 2 maddness. (actually word size maddness)
support for busblaster (maybe ?:)

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01582425224session_write_close ( )...(null):0
20.01622556840ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01622557616Database_MySQL->query( ).../DatabaseHandler.php:119
40.07452696376Database_MySQL->error( ).../Db-mysql.class.php:273